Hello Bernhard, Dr. Bernhard Kleine [2008-03-31 13:37 +0200]: > /etc/postgresql/8.3: > insgesamt 4 > drwxr-xr-x 2 root root 4096 21. Jan 06:25 main > > /etc/postgresql/8.3/main: > insgesamt 36 > -rw-r--r-- 1 root root 316 21. Jan 06:25 environment > -rw-r----- 1 postgres postgres 3621 21. Jan 06:25 pg_hba.conf > -rw-r----- 1 postgres postgres 1460 21. Jan 06:25 pg_ident.conf > -rw-r--r-- 1 postgres postgres 16650 21. Jan 06:25 postgresql.conf > -rw-r--r-- 1 root root 378 21. Jan 06:25 start.conf
Ah, so you do have a cluster configuration for an '8.3/main' cluster. > Version Cluster Port Status Owner Data directory > Log file > 7.4 main 5432 online > postgres /var/lib/postgresql/7.4/main > /var/log/postgresql/postgresql-7.4-main.log > 8.2 main 5433 online > postgres /var/lib/postgresql/8.2/main > /var/log/postgresql/postgresql-8.2-main.log > 8.3 main 5432 online > postgres /var/lib/postgresql/8.3/main > /var/log/postgresql/postgresql-8.3-main.log That's the source of the confusion. Both 7.4/main and 8.3/main are running on the same port (5432), thus the PID/process detection logic naturally gets confused. How did you get to this, did you manually change the port of the 7.4 or 8.3 cluster in postgresql.conf without checking for conflicts? I wonder whether I can detect this in postgresql-common somehow and print out a proper error message. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
