moving postgresql's data directory

From: Henry Drexler <alonup8tb(at)gmail(dot)com>
To: PGSQL-Novice <pgsql-novice(at)postgresql(dot)org>
Subject: moving postgresql's data directory
Date: 2014-01-10 14:30:22
Message-ID: CAAtgU9SV8RqoD7y4MQMDE9hVPzLUdkyDY6+SKHRfuJC1CK-iqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

First I would like to thank those in irc that have helped me, but after two
days I am going to send this beginners email in the hope that what I am
missing can be pointed out. (also after having read many online blog posts
and stackoverflow questions on this topic.)

I am just trying to move postgresql's data directory on Fedora 20,
PostgreSQL 9.3.

(background, the root partition is pretty small, and I just want to move
the data directory into my /home partition as noted below)

Here is the process I am following:

sudo systemctl stop postgresql.service
sudo mv /var/lib/pgsql/data /home/pgdata
sudo ln -s /home/pgdata/data /var/lib/pgsql/
sudo chown -R postgres:postgres /home/pgdata

Then when I go to start the service:
sudo systemctl start postgresql.service

I get this error:
Job for postgresql.service failed. See 'systemctl status
postgresql.service' and 'journalctl -xn' for details.

so I enter this:
systemctl status postgresql.service

and I get this:
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled)
Active: failed (Result: exit-code) since Fri 2014-01-10 09:23:16 EST;
4min 9s ago
Process: 19746 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
(code=exited, status=0/SUCCESS)
Process: 20497 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
Process: 20492 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
Main PID: 19576 (code=exited, status=0/SUCCESS)

I enter this:
journalctl -xn

and I get this:
-- Logs begin at Tue 2013-12-17 20:17:51 EST, end at Fri 2014-01-10
09:21:32 EST. -
Jan 10 09:10:36 localhost.localdomain gnome-session[1640]: <Window object
at 0xd9b9
Jan 10 09:11:58 localhost.localdomain gnome-session[1640]:
(tracker-miner-fs:1914):
Jan 10 09:11:58 localhost.localdomain gnome-session[1640]:
(tracker-miner-fs:1914):
Jan 10 09:17:24 localhost.localdomain gnome-session[1640]: Window manager
warning:
Jan 10 09:18:24 localhost.localdomain gnome-session[1640]: Warning:
python-keybinde
Jan 10 09:18:24 localhost.localdomain gnome-session[1640]: Unable to bind
hide_wind
Jan 10 09:21:04 localhost.localdomain gnome-session[1640]: Window manager
warning:
Jan 10 09:21:20 localhost.localdomain gnome-session[1640]: <Window object
at 0x298f
Jan 10 09:21:32 localhost.localdomain gnome-session[1640]: Warning:
python-keybinde
Jan 10 09:21:32 localhost.localdomain gnome-session[1640]: Unable to bind
hide_wind
lines 1-11/11 (END)

Any insights as to what I may have done incorrectly that is producing the
errors and preventing postgres to startup with the symlinced data folder?

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2014-01-10 15:06:16 Re: moving postgresql's data directory
Previous Message lmanorders 2014-01-09 21:31:19 Re: PQescapeLiteral in Libpq