This is more secure, and saves a redirect since we no longer accept
plain HTTP connections on the website.
References in code comments should probably be updated too, but
that doesn't seem to need back-patching, whereas this does.
Also, in the 9.2 branch, remove suggestion that you can get the
source code via FTP, since that service will be shut down soon.
Daniel Gustafsson, with a few additional changes by me
Discussion: https://postgr.es/m/
9A2C89A7-0BB8-41A8-B288-
8B7BD09D7D44@yesql.se
Release notes for all versions of PostgreSQL can be found on-line at
-http://www.postgresql.org/docs/current/static/release.html
+https://www.postgresql.org/docs/current/static/release.html
Distribution file sets include release notes for their version and preceding
versions. Visit the file doc/src/sgml/html/release.html in an HTML browser.
PostgreSQL has many language interfaces, many of which are listed here:
- http://www.postgresql.org/download
+ https://www.postgresql.org/download
See the file INSTALL for instructions on how to build and install
PostgreSQL. That file also lists supported operating systems and
instructions.
The latest version of this software may be obtained at
-http://www.postgresql.org/download/. For more information look at our
-web site located at http://www.postgresql.org/.
+https://www.postgresql.org/download/. For more information look at our
+web site located at https://www.postgresql.org/.
If you are using a git checkout, you can view the most recent installation
instructions at:
- http://www.postgresql.org/docs/devel/static/installation.html
+ https://www.postgresql.org/docs/devel/static/installation.html
Users compiling from git will also need compatible versions of Bison, Flex,
and Perl, as discussed in the install documentation. These programs are not
The TODO list is now maintained at:
- http://wiki.postgresql.org/wiki/Todo
+ https://wiki.postgresql.org/wiki/Todo
then e-mail it to pgsql-hackers@postgresql.org instead. Please use the
command "diff -c" to generate the patch.
-You may also enter a bug report at http://www.postgresql.org/ instead of
+You may also enter a bug report at https://www.postgresql.org/ instead of
e-mailing this form.
============================================================================
<listitem>
<para>
<ulink
- url="http://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD">Heap-Only
+ url="https://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD">Heap-Only
Tuples</ulink>
</para>
</listitem>
<para>
If you feel you need more introductory material, please visit the PostgreSQL
- <ulink url="http://www.postgresql.org">web site</ulink>
+ <ulink url="https://www.postgresql.org">web site</ulink>
for links to more resources.
</para>
</sect1>
<para>
Refer to the introduction in this manual or to the
<productname>PostgreSQL</productname>
-<ulink url="http://www.postgresql.org">web page</ulink>
+<ulink url="https://www.postgresql.org">web page</ulink>
for subscription information to the no-cost mailing lists.
</para>
<para>
To produce HTML documentation with the stylesheet used on <ulink
- url="http://postgresql.org/docs/current">postgresql.org</> instead of the
+ url="https://www.postgresql.org/docs/current">postgresql.org</> instead of the
default simple style use:
<screen>
<prompt>doc/src/sgml$ </prompt><userinput>make STYLE=website html</userinput>
<entry>JDBC</entry>
<entry>JDBC</entry>
<entry>Type 4 JDBC driver</entry>
- <entry><ulink url="http://jdbc.postgresql.org/"></ulink></entry>
+ <entry><ulink url="https://jdbc.postgresql.org/"></ulink></entry>
</row>
<row>
<listitem>
<para>
The <productname>PostgreSQL</productname> <ulink
- url="http://wiki.postgresql.org">wiki</ulink> contains the project's <ulink
- url="http://wiki.postgresql.org/wiki/Frequently_Asked_Questions">FAQ</>
+ url="https://wiki.postgresql.org">wiki</ulink> contains the project's <ulink
+ url="https://wiki.postgresql.org/wiki/Frequently_Asked_Questions">FAQ</>
(Frequently Asked Questions) list, <ulink
- url="http://wiki.postgresql.org/wiki/Todo">TODO</> list, and
+ url="https://wiki.postgresql.org/wiki/Todo">TODO</> list, and
detailed information about many more topics.
</para>
</listitem>
<listitem>
<para>
The <productname>PostgreSQL</productname>
- <ulink url="http://www.postgresql.org">web site</ulink>
+ <ulink url="https://www.postgresql.org">web site</ulink>
carries details on the latest release and other
information to make your work or play with
<productname>PostgreSQL</productname> more productive.
<para>
The <productname>PostgreSQL</> &version; sources can be obtained from the
download section of our
- website: <ulink url="http://www.postgresql.org/download/"></ulink>. You
+ website: <ulink url="https://www.postgresql.org/download/"></ulink>. You
should get a file named <filename>postgresql-&version;.tar.gz</filename>
or <filename>postgresql-&version;.tar.bz2</filename>. After
you have obtained the file, unpack it:
it has recently been verified to build and pass its regression tests
on that platform. Currently, most testing of platform compatibility
is done automatically by test machines in the
- <ulink url="http://buildfarm.postgresql.org/">PostgreSQL Build Farm</ulink>.
+ <ulink url="https://buildfarm.postgresql.org/">PostgreSQL Build Farm</ulink>.
If you are interested in using <productname>PostgreSQL</> on a platform
that is not represented in the build farm, but on which the code works
or can be made to work, you are strongly encouraged to set up a build
should take care of it.
</para>
- <!-- http://archives.postgresql.org/message-id/6064jt6cfm.fsf_-_@dba2.int.libertyrms.com -->
+ <!-- https://archives.postgresql.org/message-id/6064jt6cfm.fsf_-_@dba2.int.libertyrms.com -->
<para>
One user reports:
<sect3>
<title>Memory Management</title>
- <!-- http://archives.postgresql.org/message-id/603bgqmpl9.fsf@dba2.int.libertyrms.com -->
+ <!-- https://archives.postgresql.org/message-id/603bgqmpl9.fsf@dba2.int.libertyrms.com -->
<para>
AIX can be somewhat peculiar with regards to the way it does
<para>
Another method is to fill in the bug report web-form available
at the project's
- <ulink url="http://www.postgresql.org/">web site</ulink>.
+ <ulink url="https://www.postgresql.org/">web site</ulink>.
Entering a bug report this way causes it to be mailed to the
<email>pgsql-bugs@postgresql.org</email> mailing list.
</para>
A complete list of changes for each release can be obtained by
viewing the <link linkend="git">Git</link> logs for each release.
The <ulink
- url="http://archives.postgresql.org/pgsql-committers/"><literal>pgsql-committers</literal>
+ url="https://archives.postgresql.org/pgsql-committers/"><literal>pgsql-committers</literal>
email list</ulink> records all source code changes as well. There is also
- a <ulink url="http://git.postgresql.org/gitweb?p=postgresql.git;a=summary">web
+ a <ulink url="https://git.postgresql.org/gitweb?p=postgresql.git;a=summary">web
interface</ulink> that shows changes to specific files.
</para>
<title>External Resources</title>
<variablelist>
<varlistentry>
- <term><ulink url="http://wiki.postgresql.org/wiki/SEPostgreSQL">SE-PostgreSQL Introduction</ulink></term>
+ <term><ulink url="https://wiki.postgresql.org/wiki/SEPostgreSQL">SE-PostgreSQL Introduction</ulink></term>
<listitem>
<para>
This wiki page provides a brief overview, security design, architecture,
<para>
Our wiki, <ulink
- url="http://wiki.postgresql.org/wiki/Working_with_Git"></ulink>,
+ url="https://wiki.postgresql.org/wiki/Working_with_Git"></ulink>,
has some discussion on working with 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>http</>, as in:
+ prefix to <literal>https</>, as in:
<programlisting>
-git clone http://git.postgresql.org/git/postgresql.git
+git clone https://git.postgresql.org/git/postgresql.git
</programlisting>
The HTTP protocol is less efficient than the Git protocol, so it will be
<xsl:param name="html.stylesheet">
<xsl:choose>
<xsl:when test="$website.stylesheet = 0">stylesheet.css</xsl:when>
- <xsl:otherwise>http://www.postgresql.org/media/css/docs.css</xsl:otherwise>
+ <xsl:otherwise>https://www.postgresql.org/media/css/docs.css</xsl:otherwise>
</xsl:choose>
</xsl:param>