After upgrade from postgresql 9.0.3 to 9.0.3-r2, start indicates that 3 files need to be copied to /etc/postgresql with commands cp /var/lib/postgresql/9.0/data/pg_hba.conf /etc/postgresql/pg_hba.conf cp /var/lib/postgresql/9.0/data/pg_ident.conf /etc/postgresql/pg_ident.conf cp /var/lib/postgresql/9.0/data/postgresql.conf /etc/postgresql/postgresql.conf They should be cp -p /var/lib/postgresql/9.0/data/pg_hba.conf /etc/postgresql/pg_hba.conf cp -p /var/lib/postgresql/9.0/data/pg_ident.conf /etc/postgresql/pg_ident.conf cp -p /var/lib/postgresql/9.0/data/postgresql.conf /etc/postgresql/postgresql.conf otherwise postgresql will not start due to permissions Reproducible: Always
Did you run `emerge --config =dev-db/postgresql-server-9.0.3-r2' after the upgrade? I can't find the output you are referring to, so I guess it comes from something that the build system installs, e.g. pg_ctl.
No I did not run emerge --config =dev-db/postgresql-server-9.0.3-r2. Should I. I thought that was first time use. I just started started postgresql after emerge dev-db/postgresql-server-9.0.3-r2. postgresql does not started and indicates to run these commands.
No, an 'emerge --config' doesn't need to take place. But you don't have to cp the conf files either. That message is generated based on the values given for PGDATA and DATA_DIR in the related conf. This is a valid bug as I should have put that '-p' option in there.
Changed cp advice to a mv hint in the initscript. 27 Mar 2011; Aaron W. Swenson <titanofold@gentoo.org> +postgresql-server-8.2.20-r2.ebuild, +postgresql-server-8.3.14-r2.ebuild, +postgresql-server-8.4.7-r2.ebuild, +postgresql-server-9.0.3-r3.ebuild, +postgresql-server-9.1_alpha4-r1.ebuild: Fixes bugs 360031, 360029 and 359991. Removed --disable-threadsafety as scarabeus reported an issue related to it.
