Re: BUG #6200: standby bad memory allocations on SELECT

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Michael Brauwerman <michael(dot)brauwerman(at)redfin(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bridget Frey <bridget(dot)frey(at)redfin(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6200: standby bad memory allocations on SELECT
Date: 2012-01-28 22:34:23
Message-ID: CAEYLb_VDqHiysP_wgDsef7CXo7+P3tW3qSa9KR5+bWqpc=kJgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 28 January 2012 21:34, Michael Brauwerman
<michael(dot)brauwerman(at)redfin(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2012-01-28 22:48:34 Re: BUG #6412: psql & fe-connect truncate passwords
Previous Message Andy Grimm 2012-01-28 21:55:20 Re: BUG #6412: psql & fe-connect truncate passwords