From: | Serge Rielau <serge(at)rielau(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: schema variables |
Date: | 2017-11-01 05:07:59 |
Message-ID: | baaf22da-867a-4b7d-a2fb-7fa9b510c150@rielau.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
" Although the syntax of CREATE TEMPORARY TABLE resembles that of the SQL standard, the effect is not the same. In the standard, temporary tables are defined just once and automatically exist (starting with empty contents) in every session that needs them. PostgreSQL instead requires each session to issue its own CREATE TEMPORARY TABLE command for each temporary table to be used. This allows different sessions to use the same temporary table name for different purposes, whereas the standard's approach constrains all instances of a given temporary table name to have the same table structure.”
Yeah, that’s a DECLAREd table in my book. No wonder we didn’t link up.
Cheers Serge
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-11-01 05:56:03 | Re: proposal: schema variables |
Previous Message | Andreas Karlsson | 2017-11-01 04:20:02 | Re: REINDEX CONCURRENTLY 2.0 |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-11-01 05:56:03 | Re: proposal: schema variables |
Previous Message | Pavel Stehule | 2017-11-01 04:15:58 | Re: proposal: schema variables |