>>> I have a client who uses temp tables heavily, hundreds of thousands of
>>> and drops per day. They also have long running queries. The only
>>> keeps catalog bloat somewhat in check is vacuum full on bloated catalogs
>>> a few times a day. With
Actually, this is a good point ... if we dropped VACUUM FULL, we'd need
to also be able to call CLUSTER (or VACUUM REWRITE) on the system catalogs.
PostgreSQL Experts Inc.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2009-09-04 18:48:42|
|Subject: Re: Eliminating VACUUM FULL WAS: remove flatfiles.c |
|Previous:||From: Mark Reid||Date: 2009-09-04 15:15:36|
|Subject: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic|