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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Sat, 09 Feb 2008 12:19:27 -0500
  • Message-id: <24857(dot)1202577567(at)sss(dot)pgh(dot)pa(dot)us>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group