Some people have asked for the ability to create temp tables on a Hot
I've got a rough implementation plan but it would have some
restrictions, so I would like to check my understanding of the use
case for this feature so I don't waste time implementing something
nobody actually finds useful.
My understanding is that the main use cases for that would be limited
to these two options only:
1. CREATE TEMP TABLE foo AS SELECT ....
2. CREATE TEMP TABLE foo (..);
INSERT INTO foo ...
and sometimes a TRUNCATE foo;
In almost all cases people don't run multiple INSERTs, nor do they run
UPDATEs or DELETEs, so the above actions would cover 99% of use cases.
Can anyone give backup to that opinion, or alternate viewpoints?
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
pgsql-general by date
|Next:||From: Chris Travers||Date: 2011-10-27 23:24:55|
|Subject: Re: PostGIS in a commercial project|
|Previous:||From: Alan Hodgson||Date: 2011-10-27 22:23:44|
|Subject: Re: Server hitting 100% CPU usage, system comes to a crawl.|