AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Yum remove previous postgresql install12/1/2023 This is the default for the new cluster, but your old PostgreSQL 14 cluster may need to be adjusted so pg_update can access it. Set authentication to peer in pg_hba.conf for both old and new Postgres versions. (Some may be contained in the contrib package, while others are separate, such as PostGIS.) Use compatible initdb flags that match the old cluster. It contains several important points to consider: You need to use the same Postgres initdb options that were used when you ran initdb for Postgres 14.įor example, if you used the helpful data checksums feature, you need to pass the -k option to initdb, which is done indirectly via the RPM-specific postgresql-15-setup script like ~]# /usr/pgsql-15/bin/postgresql-15-setup initdbĪt this point you could start the PostgreSQL 15 server and use psql to connect to it, if you want to start with an empty database or otherwise load your data by the usual means such as with psql or pg_restore using output from pg_dump.īut if you want to convert all of your existing PostgreSQL 14 cluster’s data so everything comes over as is, you can now run pg_upgrade.įor any important system, back up your data before doing anything else, and read through the whole pg_upgrade manual. Now that we have the new PostgreSQL version installed, we can create the new database cluster. 86_64Ĭreate the new PostgreSQL 15 database cluster Package Architecture Version Repository Size Last metadata expiration check: 2:29:14 ago on Fri 09:01:38 AM MDT. We are doing system administration work here, so let’s act as system administrators and work as the root user rather than using sudo ~]# dnf install postgresql15-server postgresql15-devel postgresql15-contrib Things will be very similar on other Red Hat family members. My examples are done on the Fedora 36 x86_64 OS.
0 Comments
Read More
Leave a Reply. |