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: Sun, 10 Feb 2008 14:14:31 -0500
- Message-id: <7436(dot)1202670871(at)sss(dot)pgh(dot)pa(dot)us>
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
Home |
Main Index |
Thread Index