| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| 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:36:49 |
| Message-ID: | 21618.1339627009@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> On Wed, Jun 13, 2012 at 05:50:36PM -0400, Tom Lane wrote:
> 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.
[ reads spec more closely... ] Yeah, you're right. Will fix, thanks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2012-06-13 22:56:51 | SP-GiST for ranges based on 2d-mapping and quad-tree |
| Previous Message | Peter Eisentraut | 2012-06-13 22:31:31 | Re: Ability to listen on two unix sockets |