Greg Stark <gsstark(at)mit(dot)edu> writes:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> CREATE GLOBAL TEMP TABLE blah INHERITS myhugetable;
> I don't think you can have your temp table inherit from a real table.
Bear in mind also that this notion of a GLOBAL TEMP table has less than
nothing to do with what the standard says a GLOBAL TEMP table is. You
can't argue for the idea by claiming it increases our standards
compliance, because it actually is moving even further away. The spec
says that a temp table is a table that exists but starts empty in every
session, ie, data inserted by one session is not visible to any other
session. The GLOBAL/LOCAL choice does not affect this, it actually just
governs visibility of the table within different modules (a concept we
don't have at all).
An ALTER TABLE SET LOGGED/UNLOGGED switch might have some merit, but
please don't muddy the waters by confusing this with temp-table status.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2005-12-24 15:35:00|
|Subject: Re: [PATCHES] default resource limits|
|Previous:||From: Greg Stark||Date: 2005-12-24 15:16:52|
|Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and|