Re: Vacuuming leaked temp tables (once again) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Vacuuming leaked temp tables (once again)
Date
Msg-id 4337.1214584516@sss.pgh.pa.us
Whole thread Raw
In response to Re: Vacuuming leaked temp tables (once again)  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Vacuuming leaked temp tables (once again)  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Vacuuming leaked temp tables (once again)  ("Matthew T. O'Connor" <matthew@zeut.net>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.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


pgsql-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: MSVC 2003 compile error with pg8.3.3
Next
From: Stephen Frost
Date:
Subject: Re: Vacuuming leaked temp tables (once again)