| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, dean(dot)a(dot)rasheed(at)gmail(dot)com, er(at)xs4all(dot)nl, joel(at)compiler(dot)org, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Schema variables - new implementation for Postgres 15 |
| Date: | 2023-03-30 13:40:27 |
| Message-ID: | a76720a9-83ee-dc5d-22a8-759ac23e5808@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30.03.23 10:49, Pavel Stehule wrote:
> If I reorganize the patch to the following structure, can be it useful
> for you?
>
> 1. really basic functionality (no temporary variables, no def
> expressions, no memory cleaning)
> SELECT variable
> LET should be supported + doc, + related tests.
>
> 2. support for temporary variables (session, transaction scope),
> memory cleaning at the end of transaction
>
> 3. PL/pgSQL support
> 4. pg_dump
> 5. shadowing warning
> 6. ... others ...
That seems like an ok approach. The pg_dump support should probably go
into the first patch, so it's self-contained.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-03-30 13:41:39 | Re: running logical replication as the subscription owner |
| Previous Message | Masahiko Sawada | 2023-03-30 13:11:50 | Re: Initial Schema Sync for Logical Replication |