From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, simon(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Add ERROR msg for GLOBAL/LOCAL TEMP is not yet implemented |
Date: | 2012-06-13 22:25:31 |
Message-ID: | 20120613222531.GD32211@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 13, 2012 at 05:50:36PM -0400, Tom Lane wrote:
> Applied with some further wordsmithing on docs and comments. We can
> still tweak this if anyone objects, of course, but I thought it'd
> probably save work to get it in before the branch.
Thanks.
The SQL standard also distinguishes between global and local temporary
tables, where a local temporary table is only visible within a specific SQL
module, though its definition is still shared across sessions. Since
PostgreSQL does not support SQL modules, this distinction is not relevant in
PostgreSQL.
That new documentation paragraph describes the standard behavior for DECLARE
LOCAL TEMPORARY TABLE. CREATE LOCAL TEMPORARY TABLE produces a table
available to all modules but having one instance of its contents per module,
per session. With GLOBAL, by contrast, all modules see the same table
contents during a given session.
nm
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-06-13 22:28:08 | Re: Ability to listen on two unix sockets |
Previous Message | Peter Eisentraut | 2012-06-13 22:25:23 | Re: Ability to listen on two unix sockets |