Re: Vacuuming leaked temp tables (once again)

Michael Paesold <mpaesold@gmx.at>

From: Michael Paesold <mpaesold@gmx.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Gregory Stark <stark@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2008-06-28T00:32:50Z
Lists: pgsql-hackers
Tom Lane writes:

> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> Tom Lane wrote:
>>> 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.
>
>> I don't think this requires much of a rearrangement -- see  
>> autovacuum.c
>> 1921ff.
>
> So everyone is happy with the concept of doing it as above?  If so,
> I'll work on it this weekend sometime.

I think it is the most reasonable thing to do. Regarding the log  
messages about orphaned tables, it would be nice if you could add a  
hint/detail message explaining how to cleanup those tables. If that's  
possible.

Best Regards
Michael Paesold