Re: Internal Error on 'vacuum full' - Mailing list pgsql-bugs

From Pavan Deolasee
Subject Re: Internal Error on 'vacuum full'
Date
Msg-id 2e78013d0802272343m7a2ab51awa68e48ab6a34db53@mail.gmail.com
Whole thread Raw
In response to Internal Error on 'vacuum full'  ("Zubkovsky, Sergey" <Sergey.Zubkovsky@transas.com>)
List pgsql-bugs
On Wed, Feb 27, 2008 at 6:01 PM, Zubkovsky, Sergey
<Sergey.Zubkovsky@transas.com> wrote:
>
>
>
>
> Hi,
>
>
>
> After dropping some tables in my PG 8.3 DB I tried to execute 'vacuum full'
> command and got the error:
>
>
>
> ERROR: invalid memory alloc request size 4294967280
>
>

Hopefully this is already fixed.

http://archives.postgresql.org/pgsql-committers/2008-02/msg00101.php

The symptoms look the same. Dropping the tables would have deleted several
rows in the pg_class table and subsequent vacuuming of the table may trigger
the bug.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "vasile"
Date:
Subject: BUG #3993: RULE UPDATE : GET DIAGNOSTICS ROW_COUNT = 0
Next
From: "Sevim Mete"
Date:
Subject: FW: Bug Report - PGAdmin Version 1.6.3 - Restore