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

Re: Vacuuming leaked temp tables (once again)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Vacuuming leaked temp tables (once again)
Date: 2008-06-27 16:35:16
Message-ID: 4337.1214584516@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Could autovacuum emit log messages as soon as it sees such tables and start
> dropping them at some point later?

We might have to rearrange the logic a bit to make that happen (I'm not
sure what order things get tested in), but a log message does seem like
a good idea.  I'd go for logging anytime an orphaned table is seen,
and dropping once it's past the anti-wraparound horizon.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2008-06-27 16:36:56
Subject: Re: Vacuuming leaked temp tables (once again)
Previous:From: Hiroshi SaitoDate: 2008-06-27 16:33:03
Subject: Re: MSVC 2003 compile error with pg8.3.3

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