The recent updates to allow postgresql 7.3.x and postgresql 7.4.x
to be installed simultaneously introduced a new bug that causes
the postgresql server 'postmaster' to fail. When running
pgsql.sh start
from the postgresql74 package, a message in the log file stating
FATAL: database "postgres" does not exist
is written and 'postmaster' does not start.
The problem is that the main driver executes the startup code for
'postmaster' only if the name of the executable is 'postmaster'. The
pgsql.sh script as changed now starts the server with the binary
name 'postmaster-7.4', which is interpreted as starting postgres in
single user mode.
Attached is a patch to the main driver code that will execute the
postmaster startup code if the binary name starts with 'postmaster'
instead of having to match 'postmaster' exactly. This allows the
server to start when run as 'postmaster-7.4'.
The same patch might need to be applied to postgresql73 as well,
but I have not checked or tested that.
Patch to postgresql-7.4.3/src/backend/main/main.c
Logged In: YES
user_id=95247
I forgot to mention the package version is 7.4.3-22 in the unstable
branch. Fink version is
Package manager version: 0.20.5
Distribution version: 0.7.0.cvs
and I just performed a selfupdate on July 7th, 2004.
Logged In: YES
user_id=535292
For package-specific problems, you should try to contact
that package's Maintainer. Assigning to him...
Logged In: YES
user_id=375
Thanks, I've applied this patch to my local tree and I'm
testing now, I'll make sure it goes out with the next
postgresql release.