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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bridget Frey <bridget(dot)frey(at)redfin(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Brauwerman <michael(dot)brauwerman(at)redfin(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6200: standby bad memory allocations on SELECT
Date: 2012-01-31 15:03:07
Message-ID: 1328022138-sup-8041@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Excerpts from Bridget Frey's message of lun ene 30 18:59:08 -0300 2012:

> Anyway, here goes...

Maybe a "bt full" could give more insight into what's going on ...

> #0 0x0000003a83e30265 in raise () from /lib64/libc.so.6
> #1 0x0000003a83e31d10 in abort () from /lib64/libc.so.6
> #2 0x00000000007cb84e in errfinish (dummy=0) at elog.c:523
> #3 0x00000000007cd951 in elog_finish (elevel=22, fmt=0x95cdf0 "invalid
> memory alloc request size %lu") at elog.c:1202
> #4 0x00000000007f115c in MemoryContextAlloc (context=0x17b581d0,
> size=18446744073709551613) at mcxt.c:516
> #5 0x0000000000771a46 in text_to_cstring (t=0x17b23608) at varlena.c:139
> #6 0x0000000000770747 in varcharout (fcinfo=0x7fffd44854e0) at
> varchar.c:515

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2012-01-31 15:19:46 Re: BUG #6423: max_standby_streaming_delay does not work
Previous Message Bridget Frey 2012-01-31 13:47:57 Re: BUG #6200: standby bad memory allocations on SELECT