Re: proposal: schema variables

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Serge Rielau <serge(at)rielau(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: schema variables
Date: 2017-11-01 05:56:03
Message-ID: CAFj8pRCH1OCuSpjOkt3UhW9h3QwG0pikp+kge7Nx+JJ=Z_bPrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

2017-11-01 6:07 GMT+01:00 Serge Rielau <serge(at)rielau(dot)com>:

> "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.”
> Yeah, that’s a DECLAREd table in my book. No wonder we didn’t link up.
>

This is known discussion about local / global temp tables in PostgresSQL.
And ToDo point: implementation of global temp tables in Postgres.

This temporary behave is marginal part of proposal - so I can to remove it
from proposal - and later open discussion about CREATE TEMPORARY VARIABLE
versus DECLARE VARIABLE

Regards

Pavel

Serge

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tels 2017-11-01 07:51:38 Re: Account for cost and selectivity of HAVING quals
Previous Message Serge Rielau 2017-11-01 05:07:59 Re: proposal: schema variables

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2017-11-01 16:28:12 Re: Cursor vs Set Operation
Previous Message Serge Rielau 2017-11-01 05:07:59 Re: proposal: schema variables