Skip to main content

move postgresql datadir

How to move PostgreSQL datadir

The context

I run RHEL 7 and CentOS 7 .
The sysadmin team has setup a virtual machine for me and they put a big "/data" partition.
The default PostgreSQL installation usually use "/var/lib/pgsql" for PostgreSQL location.
I want to change it to "/data/pgsql"

How to

Stop PostgreSQL
systemctl stop postgresql

Move  "/var/lib/pgsql" and retain ownership & permissions
rsync -av /var/lib/pgsql /data/

Note: don't remove "/var/lib/pgsql" yet!

Configure "/data/pgsql/data/postgresql.conf" with the new location:
- #data_directory = 'ConfigDir'           
+ data_directory = '/data/pgsql/data'

Configure systemd service file "/usr/lib/systemd/system/postgresql.service"
- Environment=PGDATA=/var/lib/pgsql/data
+ Environment=PGDATA=/data/pgsql/data

Start PostgreSQLand check it all:
# systemctl start postgresql
# systemctl status postgresql
# ps aux | grep pgsql
# su - postgres
$ psql
postgres=#  SHOW data_directory ;
(1 row)

Warning message

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM