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 th
On Wed, 8 Apr 2009 23:59:43 +0200
Martijn van Oosterhout 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?
>
> Unfortu
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 c
On Wed, 08 Apr 2009 10:59:54 -0400
Tom Lane wrote:
> Ivan Sergio Borgonovo 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 P
Ivan Sergio Borgonovo 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 trace from
the star
