nysims4253
@nysims4253
Reviews Written
3
Average Rating
4.7
Posts
Q&A
posgresSQL ์ค์น์ ์๋ฌ ๋ด์ฉ
์๋ ํ์ธ์. docker -down -v ํด์ ๋ค์ ์ค์นํ๋ฉด ํฌํธ๋ฒํธ๋ ๋ง๊ฒ ๋ค์ด๊ฐ๋๋ฐ. ํฌํธ๊ฐ ๊ฐ๋ฐฉ์ด ์๋ผ๋๊ฒ ๊ฐ์ต๋๋ค. ; CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESfae5488c6056 postgres:latest "docker-entrypoint.sโฆ" 5 seconds ago Restarting (1) 1 second ago postgres_db '
- 0
- 3
- 93
Q&A
posgresSQL ์ค์น์ ์๋ฌ ๋ด์ฉ
์๋ ํ์ธ์. 5432ํฌํธ๋ฅผ ๋ณ๊ฒฝํด์ 5433์ผ๋ก ๋ณ๊ฒฝ์ํ๋ฉด ,docker ์์ ์คํ์๋ผ๋๋ฐ. ๋๋ค๋ฅธ ์๋ฌ๋ฉ์ธ์ง๊ฐ ๋์ค๋ค์.. ใ ใ "in 18+, these Docker images are configured to store database data in a format which is compatible with "pg_ctlcluster" (specifically, using major-version-specific directory names). This better reflects how PostgreSQL itself works, and how upgrades are to be performed. See also https://github.com/docker-library/postgres/pull/1259โ Counter to that, there appears to be PostgreSQL data in: /var/lib/postgresql/data (unused mount/volume) This is usually the result of upgrading the Docker image without upgrading the underlying database using "pg_upgrade" (which requires both versions). The suggested container configuration for 18+ is to place a single mount at /var/lib/postgresql which will then place PostgreSQL data in a subdirectory, allowing usage of "pg_upgrade --link" without mount point boundary issues. See https://github.com/docker-library/postgres/issues/37โ for a (long) discussion around this process, and suggestions for how to do so. " DB ์ค์นํ๋๋ถ๋ถ์ด ํ๋๋ค์..
- 0
- 3
- 93




