BUG #14451: PostgreSQL server on iscsi disks
The following bug has been logged on the website:
Bug reference: 14451
Logged by: Tim Klicks
Email address: tim.klicks@gmail.com
PostgreSQL version: 9.6.1
Operating system: RHEL 7.x and its derivatives
Description:
Hej all,
I just installed a RHEL 7.3 server and installed the latest 9.6.1 rpms from
your download area.
After this, I have initialized the database, shut it down and moved the
/var/lib/pgsql/9.6 folder to an iscsi volume attached to the server.
After a reboot, the postgresql server is not coming up, although the
filesystem has been mounted.
I digged a bit into this issue and found a solution and maybe a possible
"bug".
Here is the normal postgresql-9.6.service file:
.
.
.
[Unit]
Description=PostgreSQL 9.6 database server
After=syslog.target
After=network.target
.
.
.
I have now changed it to include remote-fs.target, as follows:
.
.
.
[Unit]
Description=PostgreSQL 9.6 database server
After=syslog.target
After=network.target
After=remote-fs.target
.
.
.
Now, the database is coming up as systemd knows, that the postgresql service
has to wait for the remote-fs.target to finish.
As mentioned, I am not sure if this is a bug or not, but it would be great
if you could include the remote-fs.target dependency into the
postgresql-9.6.service file.
Best Regards,
Tim.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
tim.klicks@gmail.com writes:
As mentioned, I am not sure if this is a bug or not, but it would be great
if you could include the remote-fs.target dependency into the
postgresql-9.6.service file.
I'm fairly certain this was an intentional omission. The normal
configuration does not put the database on a remote filesystem,
so adding this dependency would simply delay database startup
longer than necessary, and maybe even uselessly stop it from
coming up at all if there are problems on some remote filesystem.
The expectation is that if you rearrange things to store the DB
remotely, you should adjust the service file to match. (Perhaps
that could be documented better, though.)
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs