Jsem na to zvedav.
Jen si ted drbu hlavu:
1] kdyz nainstaluji postgresql-18 na novou VM, tak se mi inicializuje i databaze:
Setting up postgresql-18 (18.0-1.pgdg13+3) ...
Creating new PostgreSQL cluster 18/main ...
/usr/lib/postgresql/18/bin/initdb -D /var/lib/postgresql/18/main --auth-local peer --auth-host scram-sha-256 --no-instructions
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
...
2] kdyz nainstaluji postgresql-18 na VM s existujicim postgresql-17, tak se mi neinicializuje databaze:
Setting up postgresql-18 (18.0-1.pgdg13+3) ...
Setting up make-guile (4.4.1-2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12) ...
Scanning processes...
Scanning linux images...
Running kernel seems to be up-to-date.
Instalace psql je z apt.postgresql.org.
# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
995 http://apt.postgresql.org/pub/repos/apt trixie-pgdg/main amd64 Packages
release o=apt.postgresql.org,a=trixie-pgdg,n=trixie-pgdg,l=PostgreSQL for Debian/Ubuntu repository,c=main,b=amd64
origin apt.postgresql.org
Unikla mi nejaka zmena?
Ano. (Ja som si to vsimol v popise dockeroveho image):
> Important Change: the PGDATA environment variable of the image was changed to be version specific in PostgreSQL 18 and above. For 18 it is /var/lib/postgresql/18/docker. Later versions will replace 18 with their respective major version (e.g., /var/lib/postgresql/19/docker for PostgreSQL 19.x). The defined VOLUME was changed in 18 and above to /var/lib/postgresql. Mounts and volumes should be targeted at the updated location. This will allow users upgrading between PostgreSQL major releases to use the faster --link when running pg_upgrade and mounting /var/lib/postgresql.