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

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-10 19:14:31
Message-ID: 7436.1202670871@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tomas Szepe <szepe(at)pinerecords(dot)com> writes:
>> Are you doing anything that would involve lots of updates in these
>> catalogs --- maybe repeatedly renaming a column, or something like that?

> Hmm, I typically use a pair of
> "ALTER TABLE table DISABLE TRIGGER USER;"/
> "ALTER TABLE table ENABLE TRIGGER USER;"
> per almost every relation when loading a dump, other than that there's
> only the initial db creation code (lots of plpgsql triggers and a couple
> immutable functions) and then using temp tables for complicated queries.

Hm, those ALTERs wouldn't affect pg_attribute.  Maybe just using a lot
of temp tables is enough?

Are you running with autovacuum on, or not?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tomas SzepeDate: 2008-02-10 19:31:48
Subject: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Previous:From: Tomas SzepeDate: 2008-02-10 18:56:45
Subject: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group