Re: [ADMIN] Excessive growth of pg_attribute and other system tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [ADMIN] Excessive growth of pg_attribute and other system tables
Date
Msg-id 14686.1112299573@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Excessive growth of pg_attribute and other system tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [ADMIN] Excessive growth of pg_attribute and other system tables  (Steve Crawford <scrawford@pinpointresearch.com>)
List pgsql-hackers
I wrote:
> The light just went on ... system catalog updates don't generate
> statistics reports.  Hence, autovacuum doesn't know any work is needed.

The above claim is too strong --- they do normally generate stats
updates.  However, in a simple test I observed that
pg_stat_all_tables.n_tup_del did not seem to increment for the deletes
that occur when a temp table is dropped during backend exit.  (Most
likely we aren't flushing out the final stats messages...)

Steve, is your app in the habit of creating lots of temp tables that are
not dropped explicitly?  That would explain why you are getting bit more
than other people.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: Translation updates
Next
From: Alvaro Herrera
Date:
Subject: Re: Notes on lock table spilling