Re: invalid memory alloc request size 1765277700 Error Question

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Naoko Reeves <naokoreeves(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: invalid memory alloc request size 1765277700 Error Question
Date: 2012-02-24 18:30:29
Message-ID: CAOR=d=1=A0aDDH2Hod9QYEV14NYWGuSPJJ8r6hjkygNDnxXqiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 24, 2012 at 10:09 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Naoko Reeves <naokoreeves(at)gmail(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Willem Buitendyk 2012-02-24 18:31:44 Re: Upgrade to 9.1 causing function problem
Previous Message Willem Buitendyk 2012-02-24 18:20:28 Re: Upgrade to 9.1 causing function problem