postgresql suddenly died...
during recovery
2009-04-08 16:35:34 CEST FATAL: the database system is starting up
^^^ several
2009-04-08 16:35:34 CEST LOG: incomplete startup packet
2009-04-08 16:36:53 CEST FATAL: the database system is starting up
2009-04-08 16:36:53 CEST LOG: startup process
Ivan Sergio Borgonovo m...@webthatworks.it writes:
2009-04-08 16:36:53 CEST LOG: startup process (PID 3176) was
terminated by signal 11: Segmentation fault 2009-04-08 16:36:53 CEST
LOG: aborting startup due to startup process failure
Hmm, what Postgres version is this? Can you get a stack
On Wed, 08 Apr 2009 10:59:54 -0400
Tom Lane t...@sss.pgh.pa.us wrote:
Ivan Sergio Borgonovo m...@webthatworks.it writes:
2009-04-08 16:36:53 CEST LOG: startup process (PID 3176) was
terminated by signal 11: Segmentation fault 2009-04-08 16:36:53
CEST LOG: aborting startup due to startup
On Wed, Apr 08, 2009 at 05:24:08PM +0200, Ivan Sergio Borgonovo wrote:
How on Debian?
Debian does all it's automagic stuff in init. I never learned how to
start pg manually.
What might be easier is turning on core dumps (ulimit -S -c unlimited)
and then start postgres and see if it drops a
On Wed, 8 Apr 2009 23:59:43 +0200
Martijn van Oosterhout klep...@svana.org wrote:
What might be easier is turning on core dumps (ulimit -S -c
unlimited) and then start postgres and see if it drops a core
thanks.
Is there a way to just kill recovery for one DB? Just don't
start it at all?
Martijn van Oosterhout wrote:
On Wed, Apr 08, 2009 at 05:24:08PM +0200, Ivan Sergio Borgonovo wrote:
How on Debian?
Debian does all it's automagic stuff in init. I never learned how to
start pg manually.
What might be easier is turning on core dumps (ulimit -S -c unlimited)
and then start
