FS#10401 - Latest update of postgresql ( 8.3.1-1 ) breaks postgresql

Attached to Project: Arch Linux
Opened by Monika Sulik (rozoweskarpetki) - Monday, 12 May 2008, 21:12 GMT
Last edited by Paul Mattal (paul) - Tuesday, 13 May 2008, 01:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since the update (I previously used postgresql 8.2) I get the following error when trying to connect to the database:

could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

It is possible to start the postgresql daemon, but any attempt to stop it ends with the error:

pg_ctl: PID file "/var/lib/postgres/data/postmaster.pid" does not exist Is server running?

Additional info:
This concerns postgresql 8.3.1-1

Steps to reproduce:
Install the package and after starting the daemon (/etc/rc.d/postgresql start) try to use commands such as 'createdb' or 'psql' in the terminal. Also try to stop or restart the daemon.
This task depends upon

Closed by  Paul Mattal (paul)
Tuesday, 13 May 2008, 01:54 GMT
Reason for closing:  Not a bug
Comment by Eric Belanger (Snowman) - Monday, 12 May 2008, 22:06 GMT
In the log (/var/log/postgresql.log), I have:
FATAL: database files are incompatible with server
DETAIL: The data directory was initialized by PostgreSQL version 8.2, which is not compatible with this version 8.3.1.

So it seems to be a compatibility issue more than a packaging issue. I guess the content of /var/lib/postgres/data/ will need to be reinitialized somehow.
Comment by Paul Mattal (paul) - Tuesday, 13 May 2008, 01:53 GMT
As is the usual custom for PostgreSQL, x.y releases do not maintain the on-disk format and require that you do a pg_dumpall with x.y, shut down postgres, upgrade, move the old data dir out of the way, start new postgres, and then restore.

http://www.postgresql.org/docs/8.3/static/release-8-3.html

From the page:

E.2.2. Migration to Version 8.3

A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.

Loading...