Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 28 Feb 2008 13:13:19 +0530
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
- References:
- Internal Error on 'vacuum full'
- From: Zubkovsky, Sergey
- Internal Error on 'vacuum full'
- Prev by Date: BUG #3995: pqSocketCheck doesn't return
- Next by Date: Re: 8.3 problems with sspi authentication
- Previous by thread: Internal Error on 'vacuum full'
- Next by thread: BUG #3993: RULE UPDATE : GET DIAGNOSTICS ROW_COUNT = 0
- Indexes: