Re: Vacuuming leaked temp tables (once again)
От | Alvaro Herrera |
---|---|
Тема | Re: Vacuuming leaked temp tables (once again) |
Дата | |
Msg-id | 20080627165210.GH28169@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Vacuuming leaked temp tables (once again) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Vacuuming leaked temp tables (once again)
Re: Vacuuming leaked temp tables (once again) |
Список | pgsql-hackers |
Tom Lane wrote: > 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. I don't think this requires much of a rearrangement -- see autovacuum.c 1921ff. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-hackers по дате отправления: