public inbox for pgsql-performance@postgresql.org
help / color / mirror / Atom feedFrom: Pavel Luzanov <p.luzanov@postgrespro.ru>
To: Pavel Stehule <pavel.stehule@gmail.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Pavel Golub <pavel@gf.microolap.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] proposal: schema variables
Date: Mon, 12 Mar 2018 09:49:29 +0300
Message-ID: <dde8f23f-a15f-e88b-482e-5c26cce14cca@postgrespro.ru> (raw)
In-Reply-To: <CAFj8pRA6YWwV=sZj5iSgDUixr-S+u9W2+v0BJqqxHQDXS2oZww@mail.gmail.com>
References: <CAFj8pRDY+m9OOxfO10R7J0PAkCCauM-TweaTrdsrsLGMb1VbEQ@mail.gmail.com>
<623395617.20171113141500@gf.microolap.com>
<CAFj8pRDdS7ViLBJ6eA93u=C_x15EBv2deiNQDGkBS=LNrjzLLw@mail.gmail.com>
<CAFj8pRBfb-GTZSHSRVTpMzGr26-7e-_RmOmRpmuk+xuDTgC=mA@mail.gmail.com>
<CAKFQuwa00-4HTujbnYNy_OdZ2OfjUO3AX4R91DbQ1wPBZegCfg@mail.gmail.com>
<CAFj8pRBchBfyPKAVPnJKhDjh7r6kTJ9L1=etMt-pjdDzpsKOUA@mail.gmail.com>
<CAFj8pRCTsxzsxX1cWgX3cjqsSZb=gqOMd3-2FdbGz5a2+shGMg@mail.gmail.com>
<CAFj8pRA6YWwV=sZj5iSgDUixr-S+u9W2+v0BJqqxHQDXS2oZww@mail.gmail.com>
Hi,
I plan to make usability and feature test review in several days.
Is there any chances that it will work on replicas?
Such possibility is very helpful in generating reports.
Now, LET command produces an error:
ERROR: cannot execute LET in a read-only transaction
But if we say that variables are non-transactional ?
-----
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 08.03.2018 21:00, Pavel Stehule wrote:
> Hi
>
> 2018-02-07 7:34 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com
> <mailto:pavel.stehule@gmail.com>>:
>
> Hi
>
> updated patch with your changes in documentation and pg_dump
> (initial) support
>
> Main issue of this patch is storage. We can reuse local buffers
> used for temp tables. But it does allocation by 8KB and it creates
> temp files for every object. That is too big overhead. Storing
> just in session memory is too simple - then there should be lot of
> new code used, when variable will be dropped.
>
> I have ideas how to allow work with mix of scalar and composite
> types - so it will be next step of this prototype.
>
> Regards
>
> Pavel
>
>
> new update - rebased, + some initial support for composite values on
> right side and custom types, arrays are supported too.
>
> omega=# CREATE VARIABLE xx AS (a int, b numeric);
> CREATE VARIABLE
> omega=# LET xx = (10, 20)::xx;
> LET
> omega=# SELECT xx;
> +---------+
> | xx |
> +---------+
> | (10,20) |
> +---------+
> (1 row)
>
> omega=# SELECT xx.a + xx.b;
> +----------+
> | ?column? |
> +----------+
> | 30 |
> +----------+
> (1 row)
>
> omega=# \d xx
> schema variable "public.xx"
> +--------+---------+
> | Column | Type |
> +--------+---------+
> | a | integer |
> | b | numeric |
> +--------+---------+
>
>
> Regards
>
> Pavel
>
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: p.luzanov@postgrespro.ru, pavel.stehule@gmail.com, david.g.johnston@gmail.com, pavel@gf.microolap.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] proposal: schema variables
In-Reply-To: <dde8f23f-a15f-e88b-482e-5c26cce14cca@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox