DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=V7wgkREpiR8MtCfGV0XRYR10Dt+sbuxMH/7+54CQg6P9GYOibTmefjwUgIfJ2kuRyB
	KMM3RlmLL/PlfiGubcWHhRmmAGU4eIlRyECRCmAKBV3UcMkPRxmfnN1x4WNllt0gz2mE
	iK0sDuSsMkAl7eLCQX4rL7pp8NFq4sTe8ZURU=
MIME-Version: 1.0
In-Reply-To: <4BD4B44B.6030406@agliodbs.com>
References: <u2o603c8f071004231952i36642ae6u9d6a7eae6eb6ff32@mail.gmail.com>
	<4BD4B44B.6030406@agliodbs.com>
Date: Sun, 25 Apr 2010 17:54:44 -0400
Message-ID: <q2u603c8f071004251454of94da533n61da0ed02fb0f074@mail.gmail.com>
Subject: Re: global temporary tables
From: Robert Haas <robertmhaas@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 25, 2010 at 5:29 PM, Josh Berkus <josh@agliodbs.com> wrote:
> Robert,
>
>> (1). =A0What I *think* it is supposed to mean is that the table is a
>> permanent object which is "globally" visible - that is, it's part of
>> some non-temp schema like public or $user and it's column definitions
>> etc. are visible to all backends - and it's not automatically removed
>> on commit, backend exit, etc. - but the *contents* of the table are
>> temporary and backend-local, so that each new backend initially sees
>> it as empty and can then insert, update, and delete data independently
>> of what any other backend does.
>
> While closer to the standard, the above definition is a lot less useful t=
han
> what I believe a lot of people want, which is a table which is globally
> visible, but has no durability; that is, it does not get WAL-logged or
> recovered on restart. =A0Certainly this latter definition would be far mo=
re
> useful to support materialized views.

I think it's arguable which one is more useful, but I think a good
deal of the infrastructure can be made to serve both purposes, as I
further expounded upon here.

http://archives.postgresql.org/pgsql-hackers/2010-04/msg01123.php

...Robert