We get around this issue by creating a symbolic link called current that
points to the version of Postgres that we want our servers to use by
default:
ln -s /var/lib/pgsql/9.1 /var/lib/pgsql/current
The symbolic link is changed whenever we do an upgrade so it doesn't
interfere with anything that
Its because of pg_upgrade, 'in place' upgrade capabilities that are in
pg since 8.4. For that to work you need both old and new (current) set
of postgresql binaries. Etc.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On Tue, Jan 31, 2012 at 00:41, Jerry Richards
jerry.richa...@teotech.com wrote:
I just installed postgreSQL 9.1 and noticed it hard-codes the folder
/var/lib/pgsql/9.1 and it hard-codes the service name to be postgresql91.
Why is the hard-coded version included in the naming?
Note that this
I just installed postgreSQL 9.1 and noticed it hard-codes the folder
/var/lib/pgsql/9.1 and it hard-codes the service name to be postgresql91. My
previous version of 8.4.4 uses the generic folder /var/lib/pgsql/data and the
generic service name postgresql. This causes a problem for me because
On Mon, Jan 30, 2012 at 3:41 PM, Jerry Richards
jerry.richa...@teotech.com wrote:
I just installed postgreSQL 9.1 and noticed it hard-codes the folder
/var/lib/pgsql/9.1 and it hard-codes the service name to be postgresql91.
My previous version of 8.4.4 uses the generic folder
