Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > Tom Lane escribi?: > >> I rather doubt that. The most likely implementation would involve > >> cloning a "template" entry into pg_class. > > > How about a new relkind which causes the table to be located in > > PGDATA/base/<dboid>/pg_temp_<backendid>/<relfilenode> > > So each backend can have its own copy of the table with the same > > relfilenode; there's no need for extra catalog entries. > > Uh-huh. And what do you do with relpages, reltuples, relfrozenxid, and > pg_statistic entries? What if one backend wants to TRUNCATE or CLUSTER > its copy (requiring a new relfilenode)? Where does ALTER TABLE fit into > this?
And what is the use-case for this functionality? What does it give us that we don't already have? -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
