| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [HACKERS] proposal: schema variables |
| Date: | 2018-08-11 05:39:49 |
| Message-ID: | CAFj8pRDnoA3J2RM=WZJdYBXEiJUOfDv-gyJmp81Pq93jmrBb5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hi
I am sending updated patch. It should to solve almost all Giles's and
Peter's objections.
I am not happy so executor access values of variables directly. It is most
simple implementation - and I hope so it is good enough, but now the access
to variables is too volatile. But it is works good enough for usability
testing.
I am thinking about some cache of used variables in ExprContext, so the
variable in one ExprContext will look like stable - more like PLpgSQL
variables.
Regards
Pavel
| Attachment | Content-Type | Size |
|---|---|---|
| schema-variables-180811-01.patch | text/x-patch | 188.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-08-11 06:03:43 | Re: csv format for psql |
| Previous Message | David Rowley | 2018-08-11 03:32:58 | Re: [sqlsmith] ERROR: partition missing from subplans |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-08-11 18:46:34 | Re: [HACKERS] proposal: schema variables |
| Previous Message | Pavel Stehule | 2018-08-08 20:35:28 | Re: [HACKERS] proposal: schema variables |