Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL
Date: 2007-07-02 16:12:11
Message-ID: 19689F96-2FE1-4343-BE86-94317AEB0C57@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 1, 2007, at 4:46 PM, Tom Lane wrote:
>> I have question. Is correct implementation of global temp in
>> Oracle or
>> Firebird, where content of glob.temp table is session visible and
>> metadata of g.t.t is persistent?
>
> It's correct per spec. Whether it's more useful than what we do is
> highly debatable --- it forces all sessions to use the same definition
> of any given temp table name, which is a bit silly for something
> that's
> supposed to support session-local data.

Would it be possible to support both global and local?

I've often thought that having global temp tables would be a really
good idea, since it would drastically reduce the need to vacuum
catalog tables, but I've never looked into what would be required to
do so.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2007-07-02 16:18:11 Re: Postgresql.conf cleanup
Previous Message Simon Riggs 2007-07-02 15:51:10 Re: Configurable Additional Stats