Re: [HACKERS] proposal: schema variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] proposal: schema variables
Date
Msg-id CAFj8pRAnkj68ORyU7d3CtUER4-=c3oD0eU8=OLjA2UFv3orx2A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] proposal: schema variables  (srielau <serge@rielau.com>)
Responses Re: [HACKERS] proposal: schema variables  (Serge Rielau <serge@rielau.com>)
Re: [HACKERS] proposal: schema variables  (Gilles Darold <gilles.darold@dalibo.com>)
List pgsql-hackers


2017-10-31 22:28 GMT+01:00 srielau <serge@rielau.com>:
Pavel,

There is no
DECLARE TEMP CURSOR
or
DECLARE TEMP variable in PLpgSQL
and

sure .. DECLARE TEMP has no sense, I talked about similarity DECLARE and CREATE TEMP


CREATE TEMP TABLE has a different meaning from what I understand you
envision for variables.

But maybe I'm mistaken. Your original post did not describe the entire
syntax:
CREATE [TEMP] VARIABLE [IF NOT EXISTS] name AS type
  [ DEFAULT expression ] [[NOT] NULL]
  [ ON TRANSACTION END { RESET | DROP } ]
  [ { VOLATILE | STABLE } ];

Especially the TEMP is not spelled out and how its presence affects or
doesn't ON TRANSACTION END.
So may be if you elaborate I understand where you are coming from.

TEMP has same functionality (and implementation) like our temp tables - so at session end the temp variables are destroyed, but it can be assigned to transaction.







--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Re: Anyone have experience benchmarking very higheffective_io_concurrency on NVME's?
Next
From: Andreas Karlsson
Date:
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0