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

From Peter Geoghegan
Subject Re: BUG #6200: standby bad memory allocations on SELECT
Date
Msg-id CAEYLb_VDqHiysP_wgDsef7CXo7+P3tW3qSa9KR5+bWqpc=kJgg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6200: standby bad memory allocations on SELECT  (Michael Brauwerman <michael.brauwerman@redfin.com>)
Responses Re: BUG #6200: standby bad memory allocations on SELECT  (Michael Brauwerman <michael.brauwerman@redfin.com>)
List pgsql-bugs
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_PostgreS=
QL_backend_on_Linux/BSD

--=20
Peter Geoghegan =A0 =A0 =A0 http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

pgsql-bugs by date:

Previous
From: Andy Grimm
Date:
Subject: Re: BUG #6412: psql & fe-connect truncate passwords
Next
From: Tom Lane
Date:
Subject: Re: Segfault in backend CTE code