Re: Vacuuming leaked temp tables (once again)

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Vacuuming leaked temp tables (once again)
Date: 2008-06-28 00:32:50
Message-ID: 30CD5DDE-F2B6-40D6-BBFE-AE25F748488E@gmx.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-06-28 01:22:25 PATCH: CITEXT 2.0
Previous Message Andrew Hammond 2008-06-27 23:31:05 Re: the un-vacuumable table