Filip Svendsen wrote:
On Tue, Apr 29, 2008 at 8:01 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> I'm going to try to force a crash on my test server to see if I can
> find out anything more. Does anyone know how to get useful debugging
> info at the t
On Tue, Apr 29, 2008 at 8:01 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Peter Koczan" <[EMAIL PROTECTED]> writes:
> > I'm going to try to force a crash on my test server to see if I can
> > find out anything more. Does anyone know how to get useful debugging
> > info at the time of the crash? I
On Tue, Apr 29, 2008 at 1:01 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Make sure the postmaster is started under ulimit -c unlimited.
> On a depressingly large fraction of modern platforms, daemons are
> started with ulimit -c 0 by default :-(. Try putting "ulimit -c unlimited"
> into your PG
On Tue, Apr 29, 2008 at 10:35 AM, Peter Koczan <[EMAIL PROTECTED]> wrote:
>
> I'm going to try to force a crash on my test server to see if I can
> find out anything more. Does anyone know how to get useful debugging
> info at the time of the crash? I don't think I have things set to dump
> co
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> I'm going to try to force a crash on my test server to see if I can
> find out anything more. Does anyone know how to get useful debugging
> info at the time of the crash? I don't think I have things set to dump
> core anywhere, but that and/or stack tra
