Windows как обновить postgres

1. Optionally move the old cluster

   If you are using a version-specific installation directory, e.g., /opt/PostgreSQL/17, you do not need to move the old cluster. The graphical installers all use version-specific installation directories.

   If your installation directory is not version-specific, e.g., /usr/local/pgsql, it is necessary to move the current PostgreSQL install directory so it does not interfere with the new PostgreSQL installation. Once the current PostgreSQL server is shut down, it is safe to rename the PostgreSQL installation directory; assuming the old directory is /usr/local/pgsql, you can do:

   mv /usr/local/pgsql /usr/local/pgsql.old
   

   to rename the directory.

2. For source installs, build the new version

   Build the new PostgreSQL source with configure flags that are compatible with the old cluster. pg_upgrade will check pg_controldata to make sure all settings are compatible before starting the upgrade.

3. Install the new PostgreSQL binaries

   Install the new server’s binaries and support files. pg_upgrade is included in a default installation.

   For source installs, if you wish to install the new server in a custom location, use the prefix variable:

   make prefix=/usr/local/pgsql.new install
   

4. Initialize the new PostgreSQL cluster

   Initialize the new cluster using initdb. Again, use compatible initdb flags that match the old cluster. Many prebuilt installers do this step automatically. There is no need to start the new cluster.

5. Install extension shared object files

   Many extensions and custom modules, whether from contrib or another source, use shared object files (or DLLs), e.g., pgcrypto.so. If the old cluster used these, shared object files matching the new server binary must be installed in the new cluster, usually via operating system commands. Do not load the schema definitions, e.g., CREATE EXTENSION pgcrypto, because these will be duplicated from the old cluster. If extension updates are available, pg_upgrade will report this and create a script that can be run later to update them.

6. Copy custom full-text search files

   Copy any custom full text search files (dictionary, synonym, thesaurus, stop words) from the old to the new cluster.

7. Adjust authentication

   pg_upgrade will connect to the old and new servers several times, so you might want to set authentication to peer in pg_hba.conf or use a ~/.pgpass file (see Section 32.16).

8. Prepare for publisher upgrades

   pg_upgrade attempts to migrate logical slots. This helps avoid the need for manually defining the same logical slots on the new publisher. Migration of logical slots is only supported when the old cluster is version 17.0 or later. Logical slots on clusters before version 17.0 will silently be ignored.

   Before you start upgrading the publisher cluster, ensure that the subscription is temporarily disabled, by executing ALTER SUBSCRIPTION ... DISABLE. Re-enable the subscription after the upgrade.

   There are some prerequisites for pg_upgrade to be able to upgrade the logical slots. If these are not met an error will be reported.

   • The new cluster must have wal_level as logical.

   • The new cluster must have max_replication_slots configured to a value greater than or equal to the number of slots present in the old cluster.

   • The output plugins referenced by the slots on the old cluster must be installed in the new PostgreSQL executable directory.

   • The old cluster has replicated all the transactions and logical decoding messages to subscribers.

   • All slots on the old cluster must be usable, i.e., there are no slots whose pg_replication_slots.conflicting is not true.

   • The new cluster must not have permanent logical slots, i.e., there must be no slots where pg_replication_slots.temporary is false.

9. Prepare for subscriber upgrades

   Setup the subscriber configurations in the new subscriber. pg_upgrade attempts to migrate subscription dependencies which includes the subscription’s table information present in pg_subscription_rel system catalog and also the subscription’s replication origin. This allows logical replication on the new subscriber to continue from where the old subscriber was up to. Migration of subscription dependencies is only supported when the old cluster is version 17.0 or later. Subscription dependencies on clusters before version 17.0 will silently be ignored.

   There are some prerequisites for pg_upgrade to be able to upgrade the subscriptions. If these are not met an error will be reported.

   • All the subscription tables in the old subscriber should be in state i (initialize) or r (ready). This can be verified by checking pg_subscription_rel.srsubstate.

   • The replication origin entry corresponding to each of the subscriptions should exist in the old cluster. This can be found by checking pg_subscription and pg_replication_origin system tables.

   • The new cluster must have max_replication_slots configured to a value greater than or equal to the number of subscriptions present in the old cluster.

10. Stop both servers

    Make sure both database servers are stopped using, on Unix, e.g.:

    pg_ctl -D /opt/PostgreSQL/12 stop
    pg_ctl -D /opt/PostgreSQL/17 stop
    

    or on Windows, using the proper service names:

    NET STOP postgresql-12
    NET STOP postgresql-17
    

    Streaming replication and log-shipping standby servers must be running during this shutdown so they receive all changes.

11. Prepare for standby server upgrades

    If you are upgrading standby servers using methods outlined in section Step 13, verify that the old standby servers are caught up by running pg_controldata against the old primary and standby clusters. Verify that the “Latest checkpoint location” values match in all clusters. Also, make sure wal_level is not set to minimal in the postgresql.conf file on the new primary cluster.

12. Run pg_upgrade

    Always run the pg_upgrade binary of the new server, not the old one. pg_upgrade requires the specification of the old and new cluster’s data and executable (bin) directories. You can also specify user and port values, and whether you want the data files linked or cloned instead of the default copy behavior.

    If you use link mode, the upgrade will be much faster (no file copying) and use less disk space, but you will not be able to access your old cluster once you start the new cluster after the upgrade. Link mode also requires that the old and new cluster data directories be in the same file system. (Tablespaces and pg_wal can be on different file systems.) Clone mode provides the same speed and disk space advantages but does not cause the old cluster to be unusable once the new cluster is started. Clone mode also requires that the old and new data directories be in the same file system. This mode is only available on certain operating systems and file systems.

    The --jobs option allows multiple CPU cores to be used for copying/linking of files and to dump and restore database schemas in parallel; a good place to start is the maximum of the number of CPU cores and tablespaces. This option can dramatically reduce the time to upgrade a multi-database server running on a multiprocessor machine.

    For Windows users, you must be logged into an administrative account, and then run pg_upgrade with quoted directories, e.g.:

    pg_upgrade.exe
            --old-datadir "C:/Program Files/PostgreSQL/12/data"
            --new-datadir "C:/Program Files/PostgreSQL/17/data"
            --old-bindir "C:/Program Files/PostgreSQL/12/bin"
            --new-bindir "C:/Program Files/PostgreSQL/17/bin"
    

    Once started, pg_upgrade will verify the two clusters are compatible and then do the upgrade. You can use pg_upgrade --check to perform only the checks, even if the old server is still running. pg_upgrade --check will also outline any manual adjustments you will need to make after the upgrade. If you are going to be using link or clone mode, you should use the option --link or --clone with --check to enable mode-specific checks. pg_upgrade requires write permission in the current directory.

    Obviously, no one should be accessing the clusters during the upgrade. pg_upgrade defaults to running servers on port 50432 to avoid unintended client connections. You can use the same port number for both clusters when doing an upgrade because the old and new clusters will not be running at the same time. However, when checking an old running server, the old and new port numbers must be different.

    If an error occurs while restoring the database schema, pg_upgrade will exit and you will have to revert to the old cluster as outlined in Step 19 below. To try pg_upgrade again, you will need to modify the old cluster so the pg_upgrade schema restore succeeds. If the problem is a contrib module, you might need to uninstall the contrib module from the old cluster and install it in the new cluster after the upgrade, assuming the module is not being used to store user data.

13. Upgrade streaming replication and log-shipping standby servers

    If you used link mode and have Streaming Replication (see Section 26.2.5) or Log-Shipping (see Section 26.2) standby servers, you can follow these steps to quickly upgrade them. You will not be running pg_upgrade on the standby servers, but rather rsync on the primary. Do not start any servers yet.

    If you did not use link mode, do not have or do not want to use rsync, or want an easier solution, skip the instructions in this section and simply recreate the standby servers once pg_upgrade completes and the new primary is running.

    1. Install the new PostgreSQL binaries on standby servers

       Make sure the new binaries and support files are installed on all standby servers.

    2. Make sure the new standby data directories do not exist

       Make sure the new standby data directories do not exist or are empty. If initdb was run, delete the standby servers’ new data directories.

    3. Install extension shared object files

       Install the same extension shared object files on the new standbys that you installed in the new primary cluster.

    4. Stop standby servers

       If the standby servers are still running, stop them now using the above instructions.

    5. Save configuration files

       Save any configuration files from the old standbys’ configuration directories you need to keep, e.g., postgresql.conf (and any files included by it), postgresql.auto.conf, pg_hba.conf, because these will be overwritten or removed in the next step.

    6. Run rsync

       When using link mode, standby servers can be quickly upgraded using rsync. To accomplish this, from a directory on the primary server that is above the old and new database cluster directories, run this on the primary for each standby server:

       rsync --archive --delete --hard-links --size-only --no-inc-recursive old_cluster new_cluster remote_dir
       

       where old_cluster and new_cluster are relative to the current directory on the primary, and remote_dir is above the old and new cluster directories on the standby. The directory structure under the specified directories on the primary and standbys must match. Consult the rsync manual page for details on specifying the remote directory, e.g.,

       rsync --archive --delete --hard-links --size-only --no-inc-recursive /opt/PostgreSQL/12 \
             /opt/PostgreSQL/17 standby.example.com:/opt/PostgreSQL
       

       You can verify what the command will do using rsync‘s --dry-run option. While rsync must be run on the primary for at least one standby, it is possible to run rsync on an upgraded standby to upgrade other standbys, as long as the upgraded standby has not been started.

       What this does is to record the links created by pg_upgrade‘s link mode that connect files in the old and new clusters on the primary server. It then finds matching files in the standby’s old cluster and creates links for them in the standby’s new cluster. Files that were not linked on the primary are copied from the primary to the standby. (They are usually small.) This provides rapid standby upgrades. Unfortunately, rsync needlessly copies files associated with temporary and unlogged tables because these files don’t normally exist on standby servers.

       If you have tablespaces, you will need to run a similar rsync command for each tablespace directory, e.g.:

       rsync --archive --delete --hard-links --size-only --no-inc-recursive /vol1/pg_tblsp/PG_12_201909212 \
             /vol1/pg_tblsp/PG_17_202307071 standby.example.com:/vol1/pg_tblsp
       

       If you have relocated pg_wal outside the data directories, rsync must be run on those directories too.

    7. Configure streaming replication and log-shipping standby servers

       Configure the servers for log shipping. (You do not need to run pg_backup_start() and pg_backup_stop() or take a file system backup as the standbys are still synchronized with the primary.) If the old primary is prior to version 17.0, then no slots on the primary are copied to the new standby, so all the slots on the old standby must be recreated manually. If the old primary is version 17.0 or later, then only logical slots on the primary are copied to the new standby, but other slots on the old standby are not copied, so must be recreated manually.

14. Restore pg_hba.conf

    If you modified pg_hba.conf, restore its original settings. It might also be necessary to adjust other configuration files in the new cluster to match the old cluster, e.g., postgresql.conf (and any files included by it), postgresql.auto.conf.

15. Start the new server

    The new server can now be safely started, and then any rsync‘ed standby servers.

16. Post-upgrade processing

    If any post-upgrade processing is required, pg_upgrade will issue warnings as it completes. It will also generate script files that must be run by the administrator. The script files will connect to each database that needs post-upgrade processing. Each script should be run using:

    psql --username=postgres --file=script.sql postgres
    

    The scripts can be run in any order and can be deleted once they have been run.

    Caution

    In general it is unsafe to access tables referenced in rebuild scripts until the rebuild scripts have run to completion; doing so could yield incorrect results or poor performance. Tables not referenced in rebuild scripts can be accessed immediately.

17. Statistics

    Because optimizer statistics are not transferred by pg_upgrade, you will be instructed to run a command to regenerate that information at the end of the upgrade. You might need to set connection parameters to match your new cluster.

    Using vacuumdb --all --analyze-only can efficiently generate such statistics, and the use of --jobs can speed it up. Option --analyze-in-stages can be used to generate minimal statistics quickly. If vacuum_cost_delay is set to a non-zero value, this can be overridden to speed up statistics generation using PGOPTIONS, e.g., PGOPTIONS='-c vacuum_cost_delay=0' vacuumdb ....

18. Delete old cluster

    Once you are satisfied with the upgrade, you can delete the old cluster’s data directories by running the script mentioned when pg_upgrade completes. (Automatic deletion is not possible if you have user-defined tablespaces inside the old data directory.) You can also delete the old installation directories (e.g., bin, share).

19. Reverting to old cluster

    If, after running pg_upgrade, you wish to revert to the old cluster, there are several options:

    • If the --check option was used, the old cluster was unmodified; it can be restarted.

    • If the --link option was not used, the old cluster was unmodified; it can be restarted.

    • If the --link option was used, the data files might be shared between the old and new cluster:

      • If pg_upgrade aborted before linking started, the old cluster was unmodified; it can be restarted.

      • If you did not start the new cluster, the old cluster was unmodified except that, when linking started, a .old suffix was appended to $PGDATA/global/pg_control. To reuse the old cluster, remove the .old suffix from $PGDATA/global/pg_control; you can then restart the old cluster.

      • If you did start the new cluster, it has written to shared files and it is unsafe to use the old cluster. The old cluster will need to be restored from backup in this case.

Upgrading PostgreSQL Server on Windows

Upgrade Steps

1. Download and install the latest binaries

Картинка с сайта: enzedonline.com

2. Install the new server version

Картинка с сайта: enzedonline.com

On the next page, expand the Database Server category and select the newer version you want to install.

Картинка с сайта: enzedonline.com

The installer will download the necessary installation package and take you through installing the new version. At the end of this, you will be prompted to start Stack Builder once again. Deselect this and finish the installation.

3. Stop PostgreSQL services

net stop postgresql-x64-12
net stop postgresql-x64-16

Make sure you have also closed any running instances of pgadmin.

4. Configure Authentication

# IPv4 local connections:
host    all             all             127.0.0.1/32            scram-sha-256
# IPv6 local connections:
host    all             all             ::1/128                 scram-sha-256

# IPv4 local connections:
host    all             all             127.0.0.1/32            trusted
# IPv6 local connections:
host    all             all             ::1/128                 trusted

5. Upgrade the cluster with pg_upgrade

"<<new_bin_dir>>\pg_upgrade.exe"
 --old-datadir="<<old_data_dir>>"
 --new-datadir="<<new_data_dir>>"
 --old-bindir="<<old_bin_dir>>"
 --new-bindir="<<new_bin_dir>>"
 --old-port=<<old_port_number>>
 --new-port=<<new_port_number>>
 -U postgres

You will need to use the paths and versions suitable for your case. In my case, I needed to use the following:

"C:\Program Files\PostgreSQL\16\bin\pg_upgrade.exe" 
--old-datadir="C:\Program Files\PostgreSQL\12\data" 
--new-datadir="C:\Program Files\PostgreSQL\16\data" 
--old-bindir="C:\Program Files\PostgreSQL\12\bin" 
--new-bindir="C:\Program Files\PostgreSQL\16\bin" 
--old-port=5432 --new-port=5433 
-U postgres

6. Restart services

7. Test the new cluster

Run through your test regime to ensure full functionality.

8. Drop the redundant clusters

Handling Upgrade Errors

net stop postgresql-x64-16
del /S /Q "C:\Program Files\PostgreSQL\16\data\*"
"C:\Program Files\PostgreSQL\16\bin\initdb.exe" --pgdata="C:\Program Files\PostgreSQL\16\data"
net start postgresql-x64-16

Upgrading PostgreSQL Server on Ubuntu

SELECT pg_size_pretty(sum(pg_database_size(datname))) AS "Total Cluster Size"
FROM pg_database;

postgres=# \l
                                                         List of databases
     Name      |  Owner   | Encoding | Locale Provider | Collate |  Ctype  | ICU Locale | ICU Rules |       Access privileges       
---------------+----------+----------+-----------------+---------+---------+------------+-----------+-------------------------------
 some_db       | postgres | UTF8     | libc            | C.UTF-8 | C.UTF-8 |            |           | =Tc/postgres                 +
               |          |          |                 |         |         |            |           | postgres=CTc/postgres        +
               |          |          |                 |         |         |            |           | some_db_admin=CTc/postgres
 postgres      | postgres | UTF8     | libc            | C.UTF-8 | C.UTF-8 |            |           | 
 template0     | postgres | UTF8     | libc            | C.UTF-8 | C.UTF-8 |            |           | =c/postgres                  +
               |          |          |                 |         |         |            |           | postgres=CTc/postgres
 template1     | postgres | UTF8     | libc            | C.UTF-8 | C.UTF-8 |            |           | =c/postgres                  +
               |          |          |                 |         |         |            |           | postgres=CTc/postgres

dpkg --get-selections | grep postgres

sudo apt install -y postgresql-common
sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh

Upgrade Steps

1. Upgrade the core PostgreSQL packages

2. Add version specific libraries

If you list the PostgreSQL installations again, you’ll see that even though you’ve upgraded the PostgreSQL core, there is no cluster for the latest version.

dpkg --get-selections | grep postgres

sudo apt -y install postgresql-16

Repeat the listings and you’ll the version 16 server and client libraries have been added and that a version 16 cluster has also been added:

dpkg --get-selections | grep postgres

3. Stop PostgreSQL services

To safely move our database, we need to disable any services that use PostgreSQL.

sudo service postgresql stop

4. Rename the new PostgreSQL version’s default cluster.

sudo pg_renamecluster 16 main main_pristine

5. Upgrade the old cluster

Replace the version number below (12) to match your old version:

sudo pg_upgradecluster 12 main

6. Restart services

Start the services again with:

sudo service postgresql start

You should see that the old cluster is down and the new version of PostgreSQL is online:

$ pg_lsclusters
Ver Cluster       Port Status Owner    Data directory                       Log file
12  main          5435 down   postgres /var/lib/postgresql/12/main          /var/log/postgresql/postgresql-12-main.log
14  main          5433 online postgres /var/lib/postgresql/14/main          /var/log/postgresql/postgresql-14-main.log
16  main          5432 online postgres /var/lib/postgresql/16/main          /var/log/postgresql/postgresql-16-main.log
16  main_pristine 5434 online postgres /var/lib/postgresql/16/main_pristine /var/log/postgresql/postgresql-16-main_pristine.log

7. Test the new cluster

Run through your test regime to ensure full functionality.

8. Drop the redundant clusters

Once you’ve verified that the new cluster works and you no longer require the old one, you may remove it and the ‘pristine‘ cluster copy that we made above. In my case, since version 14 was leap-frogged, I can drop this as well:

sudo pg_dropcluster 12 main --stop
sudo pg_dropcluster 14 main --stop
sudo pg_dropcluster 16 main_pristine --stop

9. Clean up unused packages

sudo pg_dropcluster xx main --stop

where xx is the new version you are upgrading to.

Today we will be upgrading PostgreSql from version 14 to 15, which would be considered a Major upgrade (14->15). Below, I provide step-by-step instructions on how to do this on Windows.

Step 1: Install postgres 15 on the machine, this will create a seperate folder in the install directory /14 vs /15

• Recommend you keep the postgres user password the same

Step 2: Stop both versions of pg running on the system, here is the powershell to do that

net stop postgresql-x64-14

net stop postgresql-x64-15

Step 3: In the /data directory of each version, keep around the existing pg_hba.config files. I typcially rename them to pg_hba.conf.org

Step 4: Drop in a new pg_hba.conf in each /data directory with the following contents, this helps security getting in the way of this upgrade, full local trust

host		all		postgres		127.0.0.1/32	trust
host		all		postgres		::1/128		trust

Step 5: Upgrade Data

Our server has the bin directories located here:

C:\\Program Files\\PostgreSQL\\14\\bin
C:\\Program Files\\PostgreSQL\\15\\bin

And our data directories located here:

D:\\Data\\PgSql\\14
D:\\Data\\PgSql\\15

To upgrade the data to 15 we will be using pg_upgrade.exe. I typically like to execute this in a temp directory to isolate the files that get generated during this process. The pattern for updating via pg_upgrade.exe is as follows:

NEWVERSION\\bin\\pg_upgrade.exe --old-datadir "OLDVERSION\\data" --new-datadir "NEWVERSION\\data" --old-bindir "OLDVERSION\\bin" --new-bindir "NEWVERSION\\bin" -U USER

So for us it would be as follows (NOTE: I’m executing this command in C:\\Temp via powershell, note the & » is just to handle the space in the executable path)

& 'C:\\Program Files\\PostgreSQL\\15\\bin\\pg_upgrade.exe' --old-datadir "D:\\Data\\PgSql\\14" --new-datadir "D:\\Data\\PgSql\\15" --old-bindir "C:\\Program Files\\PostgreSQL\\14\\bin" --new-bindir "C:\\Program Files\\PostgreSQL\\15\\bin" -U postgres

Step 6: Post Upgrade: After you have a successful upgrade you still need to do a few things to get your server back up

• Copy your pg_hba.conf from the old version into your new version data directory (remove the .org also if you don’t need it)
• Update your postgresql.conf file in the new version. The install probably saw that port 5432 was in use (from the old version running) and gave you something like 5433. Change this to 5432.
• Move any SSL data over to the new version. See our ssl post here.
• Start the new server (with powershell)

  net start postgresql-x64-15

• Uninstall old version
• Clear data old version

After this, you should be up and running in version 15.

Feedback? Better Idea? General Comment?

Overview

At work I needed to upgrade from PostgreSQL from 15 to 17.
The process is not that different than upgrading in Ubuntu but there were a couple
of items that threw me off.

Perform Backup

This should be done prior to the update in case something goes wrong:

This was based on the documentation
PostgreSQL: Documentation: 17: pg_dumpall.

Note keep in mind that you should create a pgpass.conf
(or .pgpass for Linux):

This file is located C:\Users\ctyler\AppData\Roaming\postgresql
(or chmod 0600 ~/.pgpass with the right permissions).
PostgreSQL: Documentation: The Password File.

Remove admipack extension

This extension will need to be removed as it have been deprecated:

Stop Both Servers

Go to Start->Search->Serivces and stop both services:

Картинка с сайта: cetyler.github.io

Update pg_hba.conf

Make the following changes:

This remove the permissions so that you don’t error during upgrade.
This need to be done on both clusters.

Run pg_upgrade

Now let’s perform the upgrade.
Open PowerShell as Adminstrator.

I had to add ports and postgres user.
I got this info from
Upgrading PostgreSQL in Windows · GitHub
Once complete you should get:

Next Steps

After you verify that PostgreSQL 17 works as intended, you can then remove 15.
I would suggest having a backup strategy.
For example on Ubuntu, I use ZFS to create snapshots and push those snapshots to
a backup server and an external hard disk.
On Windows, I have a simple PowerShell script that will use pg_dump and
pg_dumpall.
pg_dump is for the tables that I need to backup monthly.
Most of the data in my databases come from other data sources and don’t really
need to be backed up.

The total downtime was only a couple of hours and I shouldn’t have a reason not
to upgrade PostgreSQL yearly.