Daniel Farina dan...@heroku.com writes:
A huge thanks to Conrad Irwin of Rapportive for furnishing virtually all the
details of this bug report.
This isn't really enough information to reproduce the problem ...
The occurrence rate is somewhere in the one per tens-of-millions of
queries.
...
On 09.09.2011 18:02, Tom Lane wrote:
The way that I'd personally proceed to investigate it would probably be
to change the invalid memory alloc request size size errors (in
src/backend/utils/mmgr/mcxt.c; there are about four occurrences) from
ERROR to PANIC so that they'll provoke a core dump,
On Thu, Sep 8, 2011 at 11:33 PM, Daniel Farina dan...@heroku.com wrote:
ERROR: invalid memory alloc request size 18446744073709551613
At least once, a hot standby was promoted to a primary and the errors seem
to discontinue, but then reappear on a newly-provisioned standby.
So the query
The following bug has been logged online:
Bug reference: 6201
Logged by: Jerome Schulteis
Email address: jerome.schult...@edstrom.com
PostgreSQL version: 9.0.4
Operating system: Windows XP Pro SP3
Description:Windows User Log Off Causes Backend Exception 0xC142
On 10/09/2011 4:59 AM, Jerome Schulteis wrote:
The following bug has been logged online:
Bug reference: 6201
Logged by: Jerome Schulteis
Email address: jerome.schult...@edstrom.com
PostgreSQL version: 9.0.4
Operating system: Windows XP Pro SP3
Description:Windows
