Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Szepe <szepe(at)pinerecords(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Date: 2008-02-09 17:19:27
Message-ID: 24857.1202577567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tomas Szepe <szepe(at)pinerecords(dot)com> writes:
> Trying to run "vacuum full analyze" on a ~200MB UTF8 database fails with:

> fs=> vacuum full analyze;
> WARNING: skipping "pg_authid" --- only table or database owner can vacuum it
> WARNING: skipping "pg_database" --- only table or database owner can vacuum it
> WARNING: skipping "pg_shdepend" --- only table or database owner can vacuum it
> WARNING: skipping "pg_shdescription" --- only table or database owner can vacuum it
> WARNING: skipping "pg_auth_members" --- only table or database owner can vacuum it
> ERROR: invalid memory alloc request size 4294965504

Hmm, please see if you can get a stack trace from that (set the
breakpoint at errfinish()). You might want to use vacuum verbose
first so that you can figure out which individual table is causing it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Lee Ottaway 2008-02-09 17:52:28 BUG #3947: Unable to Initialize Data Cluster
Previous Message Tomas Szepe 2008-02-09 11:52:21 8.3.0: vacuum full analyze: "invalid memory alloc request size"