#CONFIGURE POSTGRESQL DATA DIRECTORY INSTALL#

Make a backup copy of the launchd plist file, /Library/LaunchDaemons/, then edit it by changing /Applications/pfx/pgsql/data to the new data directory.Sudo mv /Applications/pfx/pgsql/data /Applications/pfx/pgsql/data.MOVED Sudo cp -rP /Applications/pfx/pgsql/data /newpath/pgsql/data This folder also houses the other main configuration files, including the nf which defines authentication settings, for both local users and other. This file is located in the data directory of the server, typically /var/lib/postgres/data. Run the following commands in a terminal. The PostgreSQL database server configuration file is nf.If it looks good, start the Supervisor service: usr/local/pfx/pgsql/bin/psql -p 50055 -U pfx -d pfx -c 'SHOW data_directory' Check that the new datadir is the one being used:.the new PostgreSQL executable directory default is the directory where pgupgrade resides environment variable PGBINNEW. the old PostgreSQL executable directory environment variable PGBINOLD. Make a backup copy of the stop script, /usr/local/pfx/qube/utils/pgsql/stop.sh, then edit it by changing the PGSQL_DATA_DIR to point to the new data directory. pgupgrade accepts the following command-line arguments: -b bindir.Optionally, you may also want to change the PGSQL_LOG to point to a new log location. Make a backup copy of the startup script, /usr/local/pfx/qube/utils/pgsql/startdb.sh, then edit it by changing the PGSQL_DATA_DIR to point to the new data directory.Mv /usr/local/pfx/pgsql/data /usr/local/pfx/pgsql/data.MOVED Rename the current datadir so that it won't be found by mistake, but leave it in place so you have a fallback plan:.Copy the current datadir over to the new location ensuring that you preserve ownership and permissions:Ĭp -rP /usr/local/pfx/pgsql/data /newpath/pgsql/data.Be logged into the Supervisor as the root user.This should be a separate physical disk, not just another partition on the same disk as other partitions, otherwise you'll get almost no benefit. The steps are more or less the same anyway.It can be advantageous to move the directory on the supervisor which contains the SQL database files from the root volume or C: drive to a filesystem on a dedicated disk.

#CONFIGURE POSTGRESQL DATA DIRECTORY INSTALL#

If not, feel free to contact me and we'll update it together.Ī fresh install is the easiest to change, but let's assume you have some databases locally you don't want to lose, just move them and restore the large database next to them.

Considering this is mostly a dump of my bash history, I hope this exact procedure works for you. The following instructions are a love letter to all those lost souls who find themselves in this situation and forget to check the status of SELinux, as well as to my future self who'll most likely have to do it again. The PostgreSQL database cluster is a directory that contains the configuration and the data. If you don't have the time, or the desire, or even a backup disc, you can always change the location where postgresql stores its data. The PGDATA variable points to the directory where the PostgreSQL. You can always resize these two partitions, but then you would have to back up your /home directory, unmount it or find a Live USB and tamper with them. At the same time, your /home partition got the rest of the disk space you had available. Let's assume that that's not nearly enough for the database you're about to restore. Most likely, you've partitioned your disk, and your root partition got the thick end of it, 50 GB if you were generous. There comes a time when you have to restore a relatively large database locally.

Configure postgresql data directory