Re: BUG #1473: Backend bus error, possibly due to ANALYZE - Mailing list pgsql-bugs

From Brian B.
Subject Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Date
Msg-id 20050211144541.GA24463@bbdab.org
Whole thread Raw
In response to Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Feb 10, 2005 at 05:24:12PM -0500, Tom Lane wrote:
> Hmm, 64meg should certainly be far past where check_stack_depth will
> start to complain, so there's something else going on here.  (BUT:
> the ulimits you see interactively aren't necessarily what the postmaster
> was started under.  You might want to confirm that the results are the
> same if you put the limits call into the boot script that launches
> the postmaster...)
I put limits in the startup script for PostgreSQL and came up with the same
64MB stacksize value.

> See debug_query_string.
I've got the gdb output of printing debug_query_string and the text saved
from script(1) is about 267KB in size. Should I send this to you off-list?


Thanks,

Brian B.

pgsql-bugs by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: BUG #1466: #maintenace_work_mem = 16384
Next
From: Tom Lane
Date:
Subject: Re: BUG #1466: #maintenace_work_mem = 16384