Fedora 40 will upgrade your PostgreSQL database from 15.6-~ to 16.1-7.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_15.6/
As root, initialize your 16.1 database: sudo postgresql-setup --initdb --unit postgresql
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_15.6/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-15/bin/ -B /usr/bin/ -d data_15.6/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is
assumed you are running them from the postgres user $home directory.
This will be your location after you enter the command in step 2. If
you for some reason change to another directory from this userid, just
remember to enter: cd $home before entering any postgresql
commands - otherwise you may not be able to execute the desired command,
or may receive a permission error. In steps 4, 9 and 10 you must issue the commands as root. If you don't have sudoers setup for the postgres user, it will fail. In this case just issue the "su" command to enter root without "sudo". Remember to issue "exit" to return to the user "postgres".
FLAC, or Free Lossless Audio Codec, is a lossless audio compression format that preserves all the original audio data. This means that FLAC files can be decoded to an identical copy of the original audio file, without any loss in quality. However, lossless compression typically results in larger file sizes than lossy compression.
FLAC is a popular format for archiving digital audio files, as well as for storing music collections on home computers. It is also becoming increasingly common for music streaming services to offer FLAC as an option for high-quality audio.
For portable devices, where storage space is limited, lossy audio formats such as MP3, AAC, and OGG Vorbis are often used. These formats can achieve much smaller file sizes than lossless formats, while still providing good sound quality.
In general, FLAC is a good choice for applications where lossless audio quality is important, such as archiving, mastering, and critical listening. Lossy formats are a good choice for applications where file size is more important, such as storing music on portable devices or streaming music over the internet.
TransFLAC: Convert FLAC to Lossy Format
TransFLAC is a command-line application that converts FLAC audio files to a lossy format at a specified quality level. It can keep both the FLAC and lossy libraries synchronized, either partially or fully. TransFLAC also synchronizes album art stored in the directory structure, such as cover, albumart, and folder files. You can run TransFLAC interactively in a terminal window, or you can schedule it to run automatically using applications such as cron or systemd.
Four parameters are required to be specified:
Input FLAC Directory: The directory to recursively search for FLAC audio files. The case of the directory name matters. TransFLAC will convert all FLAC audio files in the directory tree to the specified lossy codec format. The program will resolve any symlinks encountered and display the physical path.
Output Lossy Directory: The directory to store the lossy audio files. The case of the directory name matters. The program will resolve any symlinks encountered and display the physical path.
Lossy Codec: The codec used to convert the FLAC audio files. The case of the codec name does not matter. OPUS generally provides the best sound quality for a given file size or bitrate, and is the recommended codec. Valid values are: OPUS | OGG | AAC | MP3
Codec Quality: The quality preset used to encode the lossy audio files. The case of the quality name does not matter. OPUS STANDARD quality provides full bandwidth, stereo music, good audio quality approaching transparency, and is the recommended setting. Valid values are: LOW | MEDIUM | STANDARD | HIGH | PREMIUM
TransFLAC allows for customization of certain items in the configuration. The project wiki provides additional information.
Installation on Fedora: sudo dnf install transflac
Fedora 38 will upgrade your PostgreSQL database from 14.7-~ to 15.1-2.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_14.7/
As root, initialize your 15.1 database: sudo postgresql-setup --initdb --unit postgresql
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_14.7/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-14/bin/ -B /usr/bin/ -d data_14.7/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is
assumed you are running them from the postgres user $home directory.
This will be your location after you enter the command in step 2. If
you for some reason change to another directory from this userid, just
remember to enter: cd $home before entering any postgresql
commands - otherwise you may not be able to execute the desired command,
or may receive a permission error. In steps 4, 9 and 10 you must issue the commands as root. If you don't have sudoers setup for the postgres user, it will fail. In this case just issue the "su" command to enter root without "sudo". Remember to issue "exit" to return to the user "postgres".
Fedora 36 will upgrade your PostgreSQL database from 13.4~ to 14.1-3.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_13.4/
As root, initialize your 14.1 database: sudo postgresql-setup --initdb --unit postgresql
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_13.4/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-13/bin/ -B /usr/bin/ -d data_13.4/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is
assumed you are running them from the postgres user $home directory.
This will be your location after you enter the command in step 2. If
you for some reason change to another directory from this userid, just
remember to enter: cd $home before entering any postgresql
commands - otherwise you may not be able to execute the desired command,
or may receive a permission error.
Fedora 33 will upgrade your PostgreSQL database from 12.6~ to 13.2-6.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_12.6/
As root, initialize your 13.2 database: sudo postgresql-setup --initdb --unit postgresql
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_12.6/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-12/bin/ -B /usr/bin/ -d data_12.6/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is
assumed you are running them from the postgres user $home directory.
This will be your location after you enter the command in step 2. If
you for some reason change to another directory from this userid, just
remember to enter: cd $home before entering any postgresql
commands - otherwise you may not be able to execute the desired command,
or may receive a permission error.
Fedora 30 will upgrade your PostgreSQL database from 11.7~ to 12.2-1.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_11.7/
As root, initialize your 12.2 database: sudo postgresql-setup --initdb --unit postgresql
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_11.7/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-11/bin/ -B /usr/bin/ -d data_11.7/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is
assumed you are running them from the postgres user $home directory.
This will be your location after you enter the command in step 2. If
you for some reason change to another directory from this userid, just
remember to enter: cd $home before entering any postgresql
commands - otherwise you may not be able to execute the desired command,
or may receive a permission error.
Fedora 30 will upgrade your PostgreSQL database from 10.7~ to 11.2-3.
Since this is a major upgrade it will require that you upgrade your database.
Here is how to do it:
Install the upgrade utilities: dnf install postgresql-upgrade
Become user postgres: sudo su - postgres
Rename the data directory: mv /var/lib/pgsql/data/ /var/lib/pgsql/data_10.7/
As root, initialize your 11.2 database: sudo postgresql-setup initdb
As user postgres, Copy your pg_hba.conf: cp /var/lib/pgsql/data_10.7/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf
To avoid any potential password issues, temporarily change "md5" to "trust" in both pg_hba.conf files
Run the upgrade process: pg_upgrade -b /usr/lib64/pgsql/postgresql-10/bin/ -B /usr/bin/ -d data_10.7/ -D data
Change "trust" to md5" if you changed in step 6
Enable your postgresql.service: sudo systemctl enable postgresql.service
Start your postgresql.service: sudo systemctl start postgresql.service
Run the analyse_new_cluster.sh script as suggested
Run the delete_old_cluster.sh script as suggested
Note: When running commands as the postgres user, it is assumed you are running them from the postgres user $home directory. This will be your location after you enter the command in step 2. If you for some reason change to another directory from this userid, just remember to enter: cd $home before entering any postgresql commands - otherwise you may not be able to execute the desired command, or may receive a permission error.
