AW: [HACKERS] Another TEMP table trick - Mailing list pgsql-hackers

From Zeugswetter Andreas IZ5
Subject AW: [HACKERS] Another TEMP table trick
Date
Msg-id 219F68D65015D011A8E000006F8590C60267B2E5@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: [HACKERS] Another TEMP table trick
List pgsql-hackers
>> test=> create table test (x int);>> CREATE>> test=> insert into test values (1);>> INSERT >> test=> create temp
tabletest (x int);  <-->> CREATE                                  <-->> test=> insert into test values (2);>> INSERT
197871>> test=> select * from test;>> x>> ->> 2>> (1 row)>> >> test=> drop table test;>> DROP>> test=> select * from
test;>>x>> ->> 1>> (1 row)>> >> test=> drop table test;>> DROP
 

Do you really think that this should be allowed ? I think table names
including 
temp tables should (at least in combination with the owner) be unique. I
think your 
example above demonstrates how confusing the application code can get.

I think it is good, that temp tables are not really inserted into system
tables,
since this would be substantial overhead.
There could be a problem with GUI tools that rely on these rows
to format their output (like pgaccess or ODBC --> M$ Access) though.

Andreas



pgsql-hackers by date:

Previous
From: Vadim Mikheev
Date:
Subject: equal: don't know whether nodes of type 600 are equal
Next
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] new heap manager mmalloc