On 2010-06-13 10:54, Mladen Gogala wrote:
[...]
I have very little experience with psql, but psql's behaviour seems
similar to other vendors in this regard. It is global, but only for the
current connection. From the IBM db2 9.5 manual:

http://publib.boulder.ibm.com/infoce.../r0003272.html

The DECLARE GLOBAL TEMPORARY TABLE statement defines a temporary table
for the current session.

This behaviour also seems in accordance with the 2008 draft version of
the sql standard (5CD2-02-Foundation-2006-01.pdf, page 54)

A global temporary table is a named table defined by a <table
definition> that specifies GLOBAL TEMPORARY.
A created local temporary table is a named table defined by a <table
definition> that specifies LOCAL TEM-
PORARY. Global and created local temporary tables are effectively
materialized only when referenced in an
SQL-session. Every SQL-client module in every SQL-session that
references a created local temporary table
causes a distinct instance of that created local temporary table to be
materialized. That is, the contents of a
global temporary table or a created local temporary table cannot be
shared between SQL-sessions.

You can download draft versions of the standard from:

http://www.wiscorp.com/SQLStandards.html


/Lennart

Mladen Gogala <gogala.mladen (AT) gmail (DOT) com> wrote:
See
http://archives.postgresql.org/pgsql...4/msg01098.php
for recent discussion on psql-hackers.

-M-