PostgreSQL DB의 업그레이드는 brew postgresql-upgrade-database가 편리
11553 단어 DBRailshomebrew업그레이드PostgreSQL
brew update && brew upgrade를 실행하여 업데이트하면 PostgreSQL도 업데이트되어 버전 불일치로 인해 작동하지 않을 수 있습니다.오류 예: PG::ConnectionBad (Rails의 경우)
위의 에러 메시지를 보면 『PG(PostgreSQL) 주위의 영향일까…? 알 수 있습니다 🧐✨
╭─○ yasulab ‹2.6.5› ~/coderdojo.jp
╰─○ pg_ctl -D /usr/local/var/postgres start
waiting for server to start....2020-02-29 10:35:46.814 JST [42482] FATAL: database files are incompatible with server
2020-02-29 10:35:46.814 JST [42482] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.2.
stopped waiting
pg_ctl: could not start server
Examine the log output.
간단한 해결책
PostgreSQL 데이터베이스를 해결하려면 PostgreSQL 문서를 읽으면서 하나씩 명령을 실행해야합니다 (예 : Migrating Homebrew Postgres to a New Version).
그러나 ...!! 현재는 2018년부터 도입된 brew postgresql-upgrade-database 명령를 사용하면 Homebrew가 정리해 대응해 주어 편리합니다
╭─○ yasulab ‹2.6.5› ~/coderdojo.jp
╰─○ brew postgresql-upgrade-database
==> brew install postgresql@11
==> Downloading https://homebrew.bintray.com/bottles/[email protected]
==> Downloading from https://akamai.bintray.com/d9/d9c41a81b4314a10ba40636a2eddf2c48f15c2563754a6fcfd75a20914
######################################################################## 100.0%
==> Pouring [email protected]
==> /usr/local/Cellar/postgresql@11/11.7/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.7: 3,192 files, 36.5MB
==> Upgrading postgresql data from 11 to 12...
waiting for server to start....2020-02-29 10:40:09.308 JST [44314] LOG: listening on IPv6 address "::1", port 5432
2020-02-29 10:40:09.308 JST [44314] LOG: listening on IPv4 address "127.0.0.1", port 5432
2020-02-29 10:40:09.309 JST [44314] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2020-02-29 10:40:09.344 JST [44315] LOG: database system was interrupted; last known up at 2020-02-28 11:30:09 JST
2020-02-29 10:40:09.662 JST [44315] LOG: database system was not properly shut down; automatic recovery in progress
2020-02-29 10:40:09.667 JST [44315] LOG: redo starts at 0/39B8650
2020-02-29 10:40:09.667 JST [44315] LOG: invalid record length at 0/39B8730: wanted 24, got 0
2020-02-29 10:40:09.667 JST [44315] LOG: redo done at 0/39B86F8
2020-02-29 10:40:09.683 JST [44314] LOG: database system is ready to accept connections
done
server started
waiting for server to shut down....2020-02-29 10:40:10.039 JST [44314] LOG: received fast shutdown request
2020-02-29 10:40:10.041 JST [44314] LOG: aborting any active transactions
2020-02-29 10:40:10.041 JST [44314] LOG: background worker "logical replication launcher" (PID 44321) exited with exit code 1
2020-02-29 10:40:10.042 JST [44316] LOG: shutting down
2020-02-29 10:40:10.048 JST [44314] 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 "yasulab".
This user must also own the server process.
The database cluster will be initialized with locale "ja_JP.UTF-8".
initdb: could not find suitable text search configuration for locale "ja_JP.UTF-8"
The default text search configuration will be set to "simple".
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
그건 그렇고 ...
1점, 과거에 같은 명령으로 업그레이드 한 적이있다. 과,
postgres.old 라는 디렉트가 남아 있기 때문에, 다음과 같이 실행 도중에 멈추는 경우도 있습니다.╭─○ yasulab ‹2.6.5› ~/coderdojo.jp
╰─○ brew postgresql-upgrade-database
Error: /usr/local/var/postgres.old already exists!
Remove it if you want to upgrade data automatically.
위의 메시지에있는 것처럼 삭제해도 좋지만, 적절한 이름으로 이름을 바꾸어도 해결되므로 삭제하고 싶지 않은 경우는 적절하게 이름을 바꾸면 더 안심하네요
관련 기사
brew-postgresql-upgrade-database: add new command. #21244 - GitHub
Reference
이 문제에 관하여(PostgreSQL DB의 업그레이드는 brew postgresql-upgrade-database가 편리), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다 https://qiita.com/yasulab/items/237c3f9634055d665745텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)
좋은 웹페이지 즐겨찾기
