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

From Alvaro Herrera
Subject Re: Vacuuming leaked temp tables (once again)
Date
Msg-id 20080627164309.GG28169@alvh.no-ip.org
Whole thread Raw
In response to Re: Vacuuming leaked temp tables (once again)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost wrote:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
> > The only solution proposed in that thread was to auto-delete temp
> > tables at postmaster restart; which I opposed on the grounds that
> > throwing away data right after a crash was a terrible idea from a
> > forensic standpoint.
> 
> Why not just rename the files out of the way, and nuke the entries from
> the catalog?  Something like "filename.crash" or similar that an admin
> can have scripts in place to check for and who could then go handle as
> appropriate (remove, investigate, etc).

This was my thought too.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Vacuuming leaked temp tables (once again)
Next
From: Richard Huxton
Date:
Subject: Does anything dump per-database config settings? (was Re: ALTER DATABASE vs pg_dump)