Red Hat Bugzilla – Bug 802835
postgresql-setup needs some adjustments
Last modified: 2012-04-11 21:53:19 EDT
Description of problem:
I need to modify postgresql-setup a little before "upgrade" worked on F17:
1) service file is searched in wrong directory. Post-usrmove, service files are in /usr/lib/systemd/system, not in /lib/systemd/system
2) grep for PGPORT is mislead by comments in postgresql.service. The result: variable "PGPORT" inside postgresql-setup (druing execution) contains:
# 5433 5432
This is taken from comment explaining how to customise, inside unit file.
Version-Release number of selected component (if applicable):
thanks for report, will fix.
(In reply to comment #0)
> 1) service file is searched in wrong directory. Post-usrmove, service files are
> in /usr/lib/systemd/system, not in /lib/systemd/system
In F17, /lib is supposed to be a symlink to /usr/lib, so while I agree this needs to be changed eventually, I don't understand what actual failure you got here.
postgresql-9.1.3-2.fc16 has been submitted as an update for Fedora 16.
postgresql-9.1.3-2.fc17 has been submitted as an update for Fedora 17.
Hmm, it seem that 1) is false. I changed it during the debugging, but you are right with symlink thing, it doesn't matter.
Thanks for fix 2), it works fine now.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing postgresql-9.1.3-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
postgresql-9.1.3-3.fc17 has been submitted as an update for Fedora 17.
postgresql-9.1.3-3.fc16 has been submitted as an update for Fedora 16.
*** Bug 808256 has been marked as a duplicate of this bug. ***
postgresql-9.1.3-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
postgresql-9.1.3-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.