I had to kill -9 the postmaster process and go from there about 2
minutes after sending that email. Although the data wasn't important,
the availability of PostgreSQL on the server was. Had to get it up and
running again asap.
If it happens again, I'll attach a debugger to the postmaster process as
you've suggested and see what it thinks is going on.
Regards and best wishes,
Tom Lane wrote:
> Justin Clift <aa2(at)bigpond(dot)net(dot)au> writes:
> > Just did a :
> > pg_ctl stop -m fast
> > And the postmaster process won't die.
> Can't duplicate it here. Can you attach to the postmaster process with
> a debugger and see what it thinks its state is? The static variables in
> postmaster.c are the things to look at. Are there still entries
> in BackendList? Are any of StartupPID, ShutdownPID, CheckPointPID
> nonzero? What's the value of Shutdown? Etc.
> regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
In response to
pgsql-bugs by date
|Next:||From: Peter Eisentraut||Date: 2001-07-07 09:24:19|
|Subject: Re: Perl DBI Module fails to install correctly from RPM|
|Previous:||From: pgsql-bugs||Date: 2001-07-07 01:31:30|
|Subject: can't create timestamp field (only timestamp with time zone)|