| 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 18:46:34 |
| Message-ID: | CAFj8pRCTz_CRez3vFo_Ta_m=KtOxBGHE9+T1QG3UgRbuURfzjA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
2018-08-11 7:39 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> 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.
>
I wrote EState based schema variable values cache, so now the variables in
queries are stable (like PARAM_EXTERN) and can be used for optimization.
Regards
Pavel
>
> Regards
>
> Pavel
>
| Attachment | Content-Type | Size |
|---|---|---|
| schema-variables-180811-02.patch | text/x-patch | 193.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-11 19:15:25 | Re: [sqlsmith] ERROR: plan should not reference subplan's variable |
| Previous Message | Nico Williams | 2018-08-11 18:12:09 | Re: NetBSD vs libxml2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-08-12 05:35:33 | Re: [HACKERS] proposal: schema variables |
| Previous Message | Pavel Stehule | 2018-08-11 05:39:49 | Re: [HACKERS] proposal: schema variables |