Perhaps call them "session tables" instead of "temp tables"?
regards, tom lane
Or "transient table" ...
Maybe we can define when such table lose data
But in real - there is no need in this feature - databases are made to hold
data, not to lose.
If an application requi
> SWITCH
> CASE TABLE [IN ]
> CASE TABLE [IN ]
> CASE TABLE [IN ]
> DEFAULT [IN ]
some examples:
CREATE TABLE ttt (
id integer,
txt varchar
)
SWITCH id % 3
CASE 0 TABLE [IN ]
CASE 1 TABLE [IN ]
CASE 2 TABLE [IN ]
DEFAULT [IN ]
or
SWITCH lower(txt)
CASE 'hello' TABLE [IN ]
CASE
Original-Nachricht
> Datum: Tue, 21 Apr 2009 17:50:02 +0200
> Von: Csaba Nagy
> An: Robert Haas
> CC: Kedar Potdar , Greg Stark
> , pgsql-hackers@postgresql.org
> Betreff: Re: [HACKERS] Automating Partitions in PostgreSQL - Query on syntax
> > The big win that is associated
:54 -0300
> Von: "Dickson S. Guedes"
> An: vac...@quantentunnel.de, pgsql-hackers@postgresql.org
> Betreff: Re: [HACKERS] Automating Partitions in PostgreSQL - Query on syntax
> Vacuum, I guess you forgot to reply-to-all. ":)
>
> Em Ter, 2009-04-21 às 16:05 +02
