![]() If you work on a Mac, it's likely you use Homebrew to install packages. When you see Successfully started postgresql at the end, it means that the migration is complete and has been started, just connect again.This post will cover how to troubleshoot when the postgresql service installed via Homebrew on a Mac isn't starting. => Successfully started `postgresql` (label: ) => Your postgresql 11 data remains at /usr/local/var/postgres.old => Upgraded postgresql data from 11 to 14! Running this script will delete the old cluster's data files: usr/local/Cellar/postgresql/14.2_1/bin/vacuumdb -all -analyze-in-stages Once you start the new server, consider running: Optimizer statistics are not transferred by pg_upgrade. Restoring database schemas in the new cluster Restoring global objects in the new cluster ok Setting frozenxid and minmxid counters in new cluster ok Setting next multixact ID and offset for new cluster ok Setting next transaction ID and epoch for new cluster okĭeleting files from new pg_multixact/offsets okĬopying old pg_multixact/offsets to new server okĭeleting files from new pg_multixact/members okĬopying old pg_multixact/members to new server ok If pg_upgrade fails after this point, you must re-initdb the usr/local/Cellar/postgresql/14.2_1/bin/pg_ctl -D /usr/local/var/postgres -l logfile startĬhecking database user is the install user okĬhecking for system-defined composite types in user tables okĬhecking for reg* data types in user tables okĬhecking for contrib/isn with bigint-passing mismatch okĬhecking for user-defined encoding conversions okĬhecking for user-defined postfix operators okĬhecking for invalid "sql_identifier" user columns okĬhecking for presence of required libraries okĬhecking for new cluster tablespace directories ok You can now start the database server using: auth-local and -auth-host, the next time you run initdb. You can change this by editing pg_hba.conf or using the option -A, or Initdb: warning: enabling "trust" authentication for local connections ![]() Performing post-bootstrap initialization. Selecting dynamic shared memory implementation. The default text search configuration will be set to "english".įixing permissions on existing directory /usr/local/var/postgres. The database cluster will be initialized with locale "C". This user must also own the server process. The files belonging to this database system will be owned by user "lufei". => Moving postgresql data from /usr/local/var/postgres to /usr/local/var/postgres.old. 09:09:27.100 CST LOG: database system is shut down 09:09:27.095 CST LOG: background worker "logical replication launcher" (PID 78265) exited with exit code 1 09:09:27.094 CST LOG: aborting any active transactions 09:09:27.094 CST LOG: received fast shutdown request 09:09:26.564 CST LOG: database system is ready to accept connections 09:09:26.556 CST LOG: invalid record length at 0/16FDDF8: wanted 24, got 0 09:09:26.551 CST LOG: database system was not properly shut down automatic recovery in progress 09:09:25.607 CST LOG: database system was interrupted last known up at 19:50:23 CST => Successfully stopped `postgresql` (label: ) => Upgrading postgresql data from 11 to 14. Or, if you don 't want/need a background service you can just run: ![]() Initdb -locale =C -E UTF-8 /usr/local/var/postgres This formula has created a default database cluster with: To migrate existing data from a previous major version of PostgreSQL run:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |