Re: invalid memory alloc request size 1765277700 Error Question - Mailing list pgsql-general

From Scott Marlowe
Subject Re: invalid memory alloc request size 1765277700 Error Question
Date
Msg-id CAOR=d=1=A0aDDH2Hod9QYEV14NYWGuSPJJ8r6hjkygNDnxXqiw@mail.gmail.com
Whole thread Raw
In response to Re: invalid memory alloc request size 1765277700 Error Question  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: invalid memory alloc request size 1765277700 Error Question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Feb 24, 2012 at 10:09 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Naoko Reeves <naokoreeves@gmail.com> writes:
>> [ inconsistent behavior with a corrupted table ]
>
> I think most likely some of these queries are using a corrupted index
> and some are not --- have you looked at the EXPLAIN for each one?
> It might be a good idea to turn off enable_indexscan and
> enable_bitmapscan while poking at the table.

Could it also be a corrupted toast table?

pgsql-general by date:

Previous
From: Willem Buitendyk
Date:
Subject: Re: Upgrade to 9.1 causing function problem
Next
From: Willem Buitendyk
Date:
Subject: Re: Upgrade to 9.1 causing function problem