On Fri, Aug 06, 2010 at 03:00:35PM -0400, Tom Lane wrote: > Robert Haas <robertmh...@gmail.com> writes: > > This patch only directly addresses the issue of cleaning up the > > storage, so there are still the catalog entries to worry about. > > But it doesn't seem impossible to think about building on this > > approach to eventually handle that part of the problem better, > > too. I haven't thought too much about what that would look like, > > but I think it could be done. > > Perhaps run through pg_class after restart and flush anything marked > relistemp? Although the ideal solution, probably, would be for temp > tables to not have persistent catalog entries in the first place.
For the upcoming global temp tables, which are visible in other sessions, how would this work? Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
