database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

Remove pg_upgrade support for upgrading from pre-9.2 servers.

Browse Source 
Per discussion, we'll limit support for old servers to those branches
that can still be built easily on modern platforms, which as of now
is 9.2 and up.

Discussion: https://postgr.es/m/2923349.1634942313@sss.pgh.pa.us
This commit is contained in:
Tom Lane
2021-12-14 19:17:55 -05:00
parent 30e7c175b8
commit e469f0aaf3
9 changed files with 43 additions and 227 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/ref/pgupgrade.sgml
View File

@ -68,7 +68,7 @@ PostgreSQL documentation
</para>
<para>
pg_upgrade supports upgrades from 8.4.X and later to the current
pg_upgrade supports upgrades from 9.2.X and later to the current
major release of <productname>PostgreSQL</productname>, including snapshot and beta releases.
</para>
</refsect1>
@ -800,21 +800,6 @@ psql --username=postgres --file=script.sql postgres
(<type>regclass</type>, <type>regrole</type>, and <type>regtype</type> can be upgraded.)
</para>
<para>
If you are upgrading a pre-<productname>PostgreSQL</productname> 9.2 cluster
that uses a configuration-file-only directory, you must pass the
real data directory location to <application>pg_upgrade</application>, and
pass the configuration directory location to the server, e.g.,
<literal>-d /real-data-directory -o '-D /configuration-directory'</literal>.
</para>
<para>
If using a pre-9.1 old server that is using a non-default Unix-domain
socket directory or a default that differs from the default of the
new cluster, set <envar>PGHOST</envar> to point to the old server's socket
location. (This is not relevant on Windows.)
</para>
<para>
If you want to use link mode and you do not want your old cluster
to be modified when the new cluster is started, consider using the clone mode.