From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
Cc: | Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] proposal: schema variables |
Date: | 2018-03-08 18:00:36 |
Message-ID: | CAFj8pRA6YWwV=sZj5iSgDUixr-S+u9W2+v0BJqqxHQDXS2oZww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Hi
2018-02-07 7:34 GMT+01:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
Attachment | Content-Type | Size |
---|---|---|
schema-variables-poc-180308-01-diff | application/octet-stream | 164.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-03-08 18:06:49 | Re: FOR EACH ROW triggers on partitioned tables |
Previous Message | Robert Haas | 2018-03-08 18:00:21 | Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key |
From | Date | Subject | |
---|---|---|---|
Next Message | ldh@laurent-hasson.com | 2018-03-10 23:42:37 | RE: Updating large tables without dead tuples |
Previous Message | Rambabu V | 2018-03-06 13:27:18 | Re: by mistake dropped physical file dropped for one table. |