determined at systemd compile time from the SYS_UID_MAX setting in /etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. 1996

determined at systemd compile time from the SYS_UID_MAX setting in / etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

from the SYS_UID_MAX setting in /etc/login.defs. 562 Server Setup and Operation Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in /etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in /etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in / etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. If

determined at systemd compile time from the SYS_UID_MAX setting in / etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in / etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in / etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade

determined at systemd compile time from the SYS_UID_MAX setting in /etc/login.defs. Packaging and deployment scripts should be careful to create the postgres user as a system user by using useradd -r, adduser this option is useful for testing but should not be used when doing WAL archiving on a production deployment. This option is incompatible with --synchronous. -s interval --status-interval=interval Specifies this is because the post-upgrade steps are based on the database schemas, and not user data. For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that. pg_upgrade