This is a discussion on Internal Error on 'vacuum full' within the pgsql Bugs forums, part of the PostgreSQL category; --> Hi, After dropping some tables in my PG 8.3 DB I tried to execute 'vacuum full' command and got ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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 SQL state: XX000 Up to now the error has not reproduced once again. select version(); "PostgreSQL 8.3.0, compiled by Visual C++ build 1400" --- Sergey Zubkovsky |
| ||||
| 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...2/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 ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
| Thread Tools | |
| Display Modes | |
|
|