FS#32154 - [postgresql] needs post_install to create /run/postgresql for sysvinit-based systems

Attached to Project: Arch Linux
Opened by Neil Darlow (neildarlow) - Monday, 22 October 2012, 09:19 GMT
Last edited by Evangelos Foutras (foutrelis) - Friday, 07 December 2012, 10:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: postgresql needs post_install to run systemd-tmpfiles create for sysvinit-based systems.


Additional info:

postgresql-9.2.1-2 introduced a change of socket location to /run/postgresql which does not exist for a
sysvinit-based system at update time. It is necessary to provide a post_install script which runs:

systemd-tmpfiles --create postgresql.conf

otherwise postgresql will fail to start until the system is rebooted and sysvinit does that action for you.

Steps to reproduce:

1) Upgrade postgresql
2) Restart postgresql and observe failure to start
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Friday, 07 December 2012, 10:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in postgresql 9.2.2-1.
Comment by Marc Rechté (mrechte) - Monday, 22 October 2012, 09:34 GMT
Confirmed. To startup server I had to manually:
# mkdir /run/postgresql
# chown postgres:postgres /run/postgresql
Comment by Dan McGee (toofishes) - Monday, 22 October 2012, 12:58 GMT
Oversight on my part, sorry about this. I'll get it fixed in the next version.
Comment by Si Feng (danielfeng) - Monday, 22 October 2012, 19:10 GMT
Right. /run/postgresql was not created automatically.
Comment by Mantas Mikulėnas (grawity) - Monday, 29 October 2012, 14:38 GMT
Small note: the post_install is needed for *all* systems, not just sysvinit ones. Systemd does not automagically notice new tmpfiles.d configs.

Loading...