Skip site navigation (1) Skip section navigation (2)

Re: Internal Error on 'vacuum full'

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Zubkovsky, Sergey" <Sergey(dot)Zubkovsky(at)transas(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Internal Error on 'vacuum full'
Date: 2008-02-28 07:43:19
Message-ID: 2e78013d0802272343m7a2ab51awa68e48ab6a34db53@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, Feb 27, 2008 at 6:01 PM, Zubkovsky, Sergey
<Sergey(dot)Zubkovsky(at)transas(dot)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

In response to

pgsql-bugs by date

Next:From: Matthias MohrDate: 2008-02-28 13:45:30
Subject: Re: 8.3 problems with sspi authentication
Previous:From: Kyoko NoroDate: 2008-02-28 05:53:51
Subject: BUG #3995: pqSocketCheck doesn't return

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group