Re: Re: [COMMITTERS] pgsql: Add ERROR msg for GLOBAL/LOCAL TEMP is not yet implemented

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: simon(at)2ndQuadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Add ERROR msg for GLOBAL/LOCAL TEMP is not yet implemented
Date: 2012-06-09 21:57:31
Message-ID: 5014.1339279051@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Because the current support for temporary tables is relatively
> similar to the standard's description of LOCAL TEMPORARY TABLES, but
> nothing at all like the standard's descri0ption of GLOBAL TEMPORARY
> TABLES.

Um ... did you read the spec before stating that? In the previous
discussion of this, back in 2003, we concluded that LOCAL TEMP is
even further away from our current semantics than GLOBAL TEMP, because
the former means "local to a SQL module" and we don't have modules.

http://archives.postgresql.org/pgsql-hackers/2003-04/msg00502.php

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-06-09 22:02:44 Re: Ability to listen on two unix sockets
Previous Message Andres Freund 2012-06-09 21:45:08 Re: Ability to listen on two unix sockets