FS#31763 - [postgresql] changing PGROOT has no effect

Attached to Project: Arch Linux
Opened by Greizgh (Greizgh) - Tuesday, 02 October 2012, 08:01 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 03 October 2012, 21:00 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 0
Private No

Details

Description:
On a pure systemd system, with a fresh install of postgresql, changing the PGROOT directory in /etc/conf.d/postgresql has no effect.
After investigating in /usr/lib/systemd/system/postgresql.service, it appears that PGROOT is set to /var/lib/postgres. PIDFile also points to a file located on /var/lib/postgres/data.

I suppose arguments passed to pg_ctl take precedence on configuration file variables.

Additional info:
* postgresql 9.2.1-1
* systemd 193-1


Steps to reproduce:
pacman -S postgresql
su postgres
initdb -D '/home/postgres'
exit
vim /etc/conf.d/postgresql and change PGROOT=/home/postgres
systemctl start postgresql.service
journalctl actually show that postgresql failed, looking for data in /var/lib/postgres
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 03 October 2012, 21:00 GMT
Reason for closing:  Not a bug
Comment by Dan McGee (toofishes) - Wednesday, 03 October 2012, 21:00 GMT
Override the definitions in the service file by copying it to /etc/ and editing it; Arch has a preference to not use conf.d settings for units.

Loading...