is git.postgresql.org working fine?

Started by Jaime Casanova10 months ago4 messages
#1Jaime Casanova
jcasanov@systemguards.com.ec

Hi everyone,

I just tried to clone from git.postgresql.org and it stalled at 99% of
receiving objects, but I could clone from github without any problems.

Is it only me?

--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Jaime Casanova (#1)
Re: is git.postgresql.org working fine?

Jaime Casanova <jcasanov@systemguards.com.ec> writes:

I just tried to clone from git.postgresql.org and it stalled at 99% of
receiving objects, but I could clone from github without any problems.

Is it only me?

I've had trouble in the past with cloning on old/slow machines --- it
seems to time out after awhile. But AFAIR the symptom was an error
message not "stalling", so maybe that's unrelated.

Anyway, I tried it just now and didn't observe any problem:

$ time git clone https://git.postgresql.org/git/postgresql.git pgsql-test
Cloning into 'pgsql-test'...
remote: Enumerating objects: 20234, done.
remote: Counting objects: 100% (20234/20234), done.
remote: Compressing objects: 100% (12190/12190), done.
remote: Total 1048178 (delta 14507), reused 10293 (delta 7971), pack-reused 1027944
Receiving objects: 100% (1048178/1048178), 351.80 MiB | 20.63 MiB/s, done.
Resolving deltas: 100% (904570/904570), done.

real 0m33.110s
user 1m9.249s
sys 0m3.785s

regards, tom lane

#3Aleksander Alekseev
aleksander@timescale.com
In reply to: Tom Lane (#2)
Re: is git.postgresql.org working fine?

Hi,

Is it only me?

I've had trouble in the past with cloning on old/slow machines --- it
seems to time out after awhile. But AFAIR the symptom was an error
message not "stalling", so maybe that's unrelated.

Anyway, I tried it just now and didn't observe any problem:

[...]

For me works fine too:

```
$ time git clone git://git.postgresql.org/git/postgresql.git
Cloning into 'postgresql'...
remote: Enumerating objects: 20275, done.
remote: Counting objects: 100% (20275/20275), done.
remote: Compressing objects: 100% (12231/12231), done.
remote: Total 1048219 (delta 14543), reused 10289 (delta 7971),
pack-reused 1027944
Receiving objects: 100% (1048219/1048219), 351.78 MiB | 1.30 MiB/s, done.
Resolving deltas: 100% (904606/904606), done.
Updating files: 100% (7096/7096), done.

real 4m53.197s
user 1m51.879s
sys 0m26.096s

$ git --version
git version 2.48.1
```

--
Best regards,
Aleksander Alekseev

#4258790519
258790519@qq.com
In reply to: Aleksander Alekseev (#3)
Re: is git.postgresql.org working fine?

It seens that using git protocol is better than https

---Original---
From: "Aleksander Alekseev"<aleksander@timescale.com&gt;
Date: Wed, Mar 5, 2025 21:18 PM
To: "PostgreSQL Hackers"<pgsql-hackers@lists.postgresql.org&gt;;
Cc: "Tom Lane"<tgl@sss.pgh.pa.us&gt;;"Jaime Casanova"<jcasanov@systemguards.com.ec&gt;;
Subject: Re: is git.postgresql.org working fine?

Hi,

&gt; &gt; Is it only me?
&gt;
&gt; I've had trouble in the past with cloning on old/slow machines --- it
&gt; seems to time out after awhile. But AFAIR the symptom was an error
&gt; message not "stalling", so maybe that's unrelated.
&gt;
&gt; Anyway, I tried it just now and didn't observe any problem:
&gt;
&gt; [...]

For me works fine too:

```
$ time git clone git://git.postgresql.org/git/postgresql.git
Cloning into 'postgresql'...
remote: Enumerating objects: 20275, done.
remote: Counting objects: 100% (20275/20275), done.
remote: Compressing objects: 100% (12231/12231), done.
remote: Total 1048219 (delta 14543), reused 10289 (delta 7971),
pack-reused 1027944
Receiving objects: 100% (1048219/1048219), 351.78 MiB | 1.30 MiB/s, done.
Resolving deltas: 100% (904606/904606), done.
Updating files: 100% (7096/7096), done.

real 4m53.197s
user 1m51.879s
sys 0m26.096s

$ git --version
git version 2.48.1
```

--
Best regards,
Aleksander Alekseev