Re: BUG #6200: standby bad memory allocations on SELECT - Mailing list pgsql-bugs

From Michael Brauwerman
Subject Re: BUG #6200: standby bad memory allocations on SELECT
Date
Msg-id CAHDXJ6j6Oyke3z_eNSqA1O8G+3M359c3r5NjUp25F5sRUmSPDA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6200: standby bad memory allocations on SELECT  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: BUG #6200: standby bad memory allocations on SELECT  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
We did try that with a postgres 9.1.2, compiled from source with debug
flags, but we got 0x10 bad address in gdb. (Obviously we did it wrong
somehow)

We will keep trying to get a good set of symbols set up.
On Jan 28, 2012 2:34 PM, "Peter Geoghegan" <peter@2ndquadrant.com> wrote:

> On 28 January 2012 21:34, Michael Brauwerman
> <michael.brauwerman@redfin.com> wrote:
> > We have the (5GB) core file, and are happy to do any more forensics
> anyone
> > can advise.
>
> Ideally, you'd be able to install debug information packages, which
> should give a more detailed and useful stack trace, as described here:
>
>
> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>
> --
> Peter Geoghegan       http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training and Services
>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: wCTE cannot be used to update parent inheritance table
Next
From: Tom Lane
Date:
Subject: Re: Documentation bug regarding collations