Since some time back, we have deployed the git server side http handler on
git.postgresql.org, so the instructions currently on the site are incorrect
in saying that git:// is faster than https://. In fact, we have some
reports and testing that https:// can be significantly faster (due to other
reasons). https is also a protocol that's a lot less likely to run into
firewall issues etc.
Based on that, I propose the following patch which both moves https:// up
to being the first-hand choice for protocol, and removes the references to
it being slower.
Thoughts?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
diff --git a/doc/src/sgml/sourcerepo.sgml b/doc/src/sgml/sourcerepo.sgml
index 8729a8450d..c3582ec3e9 100644
--- a/doc/src/sgml/sourcerepo.sgml
+++ b/doc/src/sgml/sourcerepo.sgml
@@ -52,7 +52,7 @@
To begin using the Git repository, make a clone of the official mirror:
<programlisting>
-git clone git://git.postgresql.org/git/postgresql.git
+git clone https://git.postgresql.org/git/postgresql.git
</programlisting>
This will copy the full repository to your local machine, so it may take
@@ -62,16 +62,13 @@ git clone git://git.postgresql.org/git/postgresql.git
</para>
<para>
- The Git mirror can also be reached via the HTTP protocol, if for example
- a firewall is blocking access to the Git protocol. Just change the URL
- prefix to <literal>https</literal>, as in:
+ The Git mirror can also be reached via the older Git protocol. Just change the URL
+ prefix to <literal>git</literal>, as in:
<programlisting>
-git clone https://git.postgresql.org/git/postgresql.git
+git clone git://git.postgresql.org/git/postgresql.git
</programlisting>
- The HTTP protocol is less efficient than the Git protocol, so it will be
- slower to use.
</para>
</step>
