On Tue, Oct 19, 2010 at 12:03 PM, Robert Haas <robertmh...@gmail.com> wrote: > The trick is that it would require us to have two pg_class tables, two > pg_attribute tables, two pg_attrdef tables, etc.: in each case, one > permanent and one temporary. I am not sure how complex that will turn > out to be.
Tom suggested using inheritance for this. I find it strange to try constructing catalog tables to represent these local definitions which never need to be read by any other backend and in any case are 1:1 copies of the global catalog entries. It seems to me simpler and more direct to just nail relcache entries for these objects into memory and manipulate them directly. They can be constructed from the global catalog tables and then tweaked to point to the backend local temporary tables. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
