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? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings