839の日記

業務とは関係ない趣味の話を書くブログです。

macOSのpostgresqlを更新する

メジャーバージョンアップがあるたびに調べているので次から自分のブログ内で検索を完結できるように書いておく。 今回はbrewで入れたpostgres11から12に更新する作業を行った。

TLDR

brew postgresql-upgrade-database を叩くと移行が完了する。 ただし古いpostgresが残ってしまうので移行後に brew uninstall postgresql@11 を行っておくほうが良さそう。

補足

雑に brew upgrade を行ったら11から12に上がってしまい、psqlコマンドが失敗するようになっていたのでどうやって更新するんだったかなぁと調べた。 つまりバージョンを上げてしまった後に上記の移行コマンドを叩いても特に問題はない。 他の記事では上げる前にあれこれする手順も紹介されているが、macOSに関して言うと上げてしまった後に1コマンド叩くだけで移行が完了するのでとても楽だった。

壊れてた時期もあったらしいけど自分が試したときには問題なかった。
refs: brew postgresql-upgrade-database fails 11 -> 12 · Issue #47110 · Homebrew/homebrew-core · GitHub

メモ用の実行ログ

$ > brew postgresql-upgrade-database
==> brew install postgresql@11
==> Downloading https://homebrew.bintray.com/bottles/postgresql@11-11.6.catalina.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/c9/c91e358723fd5f700f059a0a1beff478d3e4aaa2ec40a3a166e946ff130d9fd0?__gda__=exp=1576910868~hmac=6529fbd707d31b831a1a4abfe051201c23004a0ea2b8a5cc271a6b0809c0ebb9&response-content-disposition=attachment%3Bfilename%3D%22postgresql%40
######################################################################## 100.0%
==> Pouring postgresql@11-11.6.catalina.bottle.tar.gz
==> /usr/local/Cellar/postgresql@11/11.6/bin/initdb --locale=C -E UTF-8 /usr/local/var/postgresql@11
==> Caveats
To migrate existing data from a previous major version of PostgreSQL run:
  brew postgresql-upgrade-database

postgresql@11 is keg-only, which means it was not symlinked into /usr/local,
because this is an alternate version of another formula.

If you need to have postgresql@11 first in your PATH run:
  echo 'export PATH="/usr/local/opt/postgresql@11/bin:$PATH"' >> ~/.zshrc

For compilers to find postgresql@11 you may need to set:
  export LDFLAGS="-L/usr/local/opt/postgresql@11/lib"
  export CPPFLAGS="-I/usr/local/opt/postgresql@11/include"

For pkg-config to find postgresql@11 you may need to set:
  export PKG_CONFIG_PATH="/usr/local/opt/postgresql@11/lib/pkgconfig"


To have launchd start postgresql@11 now and restart at login:
  brew services start postgresql@11
Or, if you don't want/need a background service you can just run:
  pg_ctl -D /usr/local/var/postgresql@11 start
==> Summary
🍺  /usr/local/Cellar/postgresql@11/11.6: 3,191 files, 36.4MB
==> Upgrading postgresql data from 11 to 12...
Stopping `postgresql`... (might take a while)
==> Successfully stopped `postgresql` (label: homebrew.mxcl.postgresql)
waiting for server to start....2019-12-21 15:36:11.543 JST [28763] LOG:  listening on IPv6 address "::1", port 5432
2019-12-21 15:36:11.543 JST [28763] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2019-12-21 15:36:11.543 JST [28763] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2019-12-21 15:36:11.615 JST [28764] LOG:  database system was interrupted; last known up at 2019-12-18 23:10:29 JST
2019-12-21 15:36:12.543 JST [28764] LOG:  database system was not properly shut down; automatic recovery in progress
2019-12-21 15:36:12.557 JST [28764] LOG:  redo starts at 28/787E54F0
2019-12-21 15:36:12.557 JST [28764] LOG:  invalid record length at 28/787E55D0: wanted 24, got 0
2019-12-21 15:36:12.557 JST [28764] LOG:  redo done at 28/787E5598
.2019-12-21 15:36:12.586 JST [28763] LOG:  database system is ready to accept connections
 done
server started
waiting for server to shut down....2019-12-21 15:36:13.010 JST [28763] LOG:  received fast shutdown request
2019-12-21 15:36:13.010 JST [28763] LOG:  aborting any active transactions
2019-12-21 15:36:13.011 JST [28763] LOG:  background worker "logical replication launcher" (PID 28770) exited with exit code 1
2019-12-21 15:36:13.011 JST [28765] LOG:  shutting down
2019-12-21 15:36:13.017 JST [28763] LOG:  database system is shut down
 done
server stopped
==> Moving postgresql data from /usr/local/var/postgres to /usr/local/var/postgres.old...
==> Creating database...
The files belonging to this database system will be owned by user "xxxx".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /usr/local/var/postgres ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Asia/Tokyo
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    /usr/local/opt/postgresql/bin/pg_ctl -D /usr/local/var/postgres -l logfile start

==> Migrating and upgrading data...
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for reg* data types in user tables                 ok
Checking for contrib/isn with bigint-passing mismatch       ok
Checking for tables WITH OIDS                               ok
Checking for invalid "sql_identifier" user columns          ok
Creating dump of global objects                             ok
Creating dump of database schemas
                                                            ok
Checking for presence of required libraries                 ok
Checking database user is the install user                  ok
Checking for prepared transactions                          ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade
------------------
Analyzing all rows in the new cluster                       ok
Freezing all rows in the new cluster                        ok
Deleting files from new pg_xact                             ok
Copying old pg_xact to new server                           ok
Setting next transaction ID and epoch for new cluster       ok
Deleting files from new pg_multixact/offsets                ok
Copying old pg_multixact/offsets to new server              ok
Deleting files from new pg_multixact/members                ok
Copying old pg_multixact/members to new server              ok
Setting next multixact ID and offset for new cluster        ok
Resetting WAL archives                                      ok
Setting frozenxid and minmxid counters in new cluster       ok
Restoring global objects in the new cluster                 ok
Restoring database schemas in the new cluster
                                                            ok
Copying user relation files
                                                            ok
Setting next OID for new cluster                            ok
Sync data directory to disk                                 ok
Creating script to analyze new cluster                      ok
Creating script to delete old cluster                       ok

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
    ./analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
    ./delete_old_cluster.sh
==> Upgraded postgresql data from 11 to 12!
==> Your postgresql 11 data remains at /usr/local/var/postgres.old
==> Successfully started `postgresql` (label: homebrew.mxcl.postgresql)