Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e9lHr-0006tm-TM for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Nov 2017 05:10:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e9lHq-0003Oj-D8 for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Nov 2017 05:09:58 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9lGH-0000aT-Ij for pgsql-hackers@postgresql.org; Wed, 01 Nov 2017 05:08:21 +0000 Received: from p3plsmtpa07-06.prod.phx3.secureserver.net ([173.201.192.235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9lGE-0007D2-ES for pgsql-hackers@postgresql.org; Wed, 01 Nov 2017 05:08:20 +0000 Received: from [54.210.254.214] ([54.210.254.214]) by :SMTPAUTH: with SMTP id 9lGBexGqKxTUN9lGCeOeWn; Tue, 31 Oct 2017 22:08:16 -0700 Content-Type: multipart/alternative; boundary="----sinikael-?=_1-15095128965170.171786597231403" From: Serge Rielau To: Pavel Stehule Cc: PostgreSQL Hackers In-Reply-To: References: <20171026220732.GI4496@localhost> <1509399760322-0.post@n3.nabble.com> <5665be80-1772-4998-8dbc-3bd071c0d9ad@rielau.com> <1509485317393-0.post@n3.nabble.com> Subject: Re: proposal: schema variables Message-Id: Date: Tue, 31 Oct 2017 22:07:59 -0700 X-Cm-Message-Id: 1509512880205739ec71bd6d7f4eb3766f4bb7845bf83ce759f956b0324591681336044 X-Cm-Draft-Id: WyJhIiwzLCJkcmFmdF9pZCIsIjE1MDk1MTI4Nzk3NTIiLCJ2IiwxXQ== X-Cm-Tracking-Code: 2.0/1509512879/647b813270dffd4c4b2631f3c9eb3f46/3/9cf3801d03770ada01bb39dc8f52321d/f0f5edb1e2c00603f7c4bf7c83243f2a/619f5dd6cf0c728abb479c46d4dbfbe4 X-Mailer: Newton MIME-Version: 1.0 X-CMAE-Envelope: MS4wfNiIdglCgkegqAAT5rJ0XLr4eqVLV1okE4SWZJ50vCDM2edED7aCzOjpGhzpaSys1Seo7dd+GWuMwBJAODVx5xnRswJAmZN1gSbMC1/QRENZ0tVGxR5S qY7V7V7bcv6LR4HXsQOQMNIP9czmpNaSE7TMySIef2AqlWPZtmzyxql1bzIXbBBefJ+FvWgnhb9New== List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org ------sinikael-?=_1-15095128965170.171786597231403 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable " Although the syntax of CREATE TEMPORARY TABLE resembles that of the SQL = standard, the effect is not the same. In the standard, temporary tables are= defined just once and automatically exist (starting with empty contents) = in every session that needs them. PostgreSQL instead requires each session = to issue its own CREATE TEMPORARY TABLE command for each temporary table to= be used. This allows different sessions to use the same temporary table = name for different purposes, whereas the standard's approach constrains all= instances of a given temporary table name to have the same table structure= .=E2=80=9D Yeah, that=E2=80=99s a DECLAREd table in my book. No wonder we = didn=E2=80=99t link up. Cheers Serge ------sinikael-?=_1-15095128965170.171786597231403 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
"Although the = syntax of CREATE TEMPORARY = TABLE resembles = that of the SQL standard, the effect is not the same. In the standard, = temporary tables are defined just once and automatically exist (starting = with empty contents) in every session that needs them. PostgreSQL instead requires each session to issue its own CREATE TEMPORARY TABLE command for = each temporary table to be used. This allows different sessions to use the = same temporary table name for different purposes, whereas the standard's = approach constrains all instances of a given temporary table name to have = the same table structure.=E2=80=9D
Yeah,=  that= =E2=80=99s a DECLAREd table in my book. No wonder we didn=E2=80=99t link up= .

Cheers
Serge
------sinikael-?=_1-15095128965170.171786597231403--