| From: | Michael Brauwerman <michael(dot)brauwerman(at)redfin(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Bridget Frey <bridget(dot)frey(at)redfin(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: BUG #6200: standby bad memory allocations on SELECT |
| Date: | 2012-01-29 01:45:00 |
| Message-ID: | CAHDXJ6j6Oyke3z_eNSqA1O8G+3M359c3r5NjUp25F5sRUmSPDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)2ndquadrant(dot)com> wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-01-29 01:56:42 | Re: Documentation bug regarding collations |
| Previous Message | Tom Lane | 2012-01-29 01:27:10 | Re: wCTE cannot be used to update parent inheritance table |