Re: [HACKERS] proposal: schema variables

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-12 05:35:33
Message-ID: CAFj8pRA_jZYuTRHEMsv8CnZLBqmnS5xRjcZh-uf0nBWA7WrzMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi

2018-08-11 20:46 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:

>
>
> 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.
>

new update - after cleaning

Regards

Pavel

> Regards
>
> Pavel
>
>
>>
>> Regards
>>
>> Pavel
>>
>
>

Attachment Content-Type Size
schema-variables-180812-01.patch text/x-patch 194.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-08-12 05:42:50 Re: [HACKERS] Optional message to user when terminating/cancelling backend
Previous Message Edmund Horner 2018-08-12 02:29:05 Tid scan improvements