From: | Tomas Szepe <szepe(at)pinerecords(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | 8.3.0: vacuum full analyze: "invalid memory alloc request size" |
Date: | 2008-02-09 11:52:21 |
Message-ID: | 20080209115221.GA27757@louise.pinerecords.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello,
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
But not always, sometimes it goes through w/o a problem:
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
WARNING: skipping "pg_tablespace" --- only table or database owner can vacuum it
WARNING: skipping "pg_pltemplate" --- only table or database owner can vacuum it
VACUUM
This is on x86 Linux. 8.2.6 does not exhibit the problem, or at least I haven't
run into it. What info do I need to submit so that this can be tracked down?
Best regards,
--
Tomas Szepe <szepe(at)pinerecords(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-09 17:19:27 | Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" |
Previous Message | Holger Klawitter | 2008-02-08 22:20:18 | BUG #3945: unexpected ON INSERT rule behaviour |