Re: [HACKERS] proposal: schema variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] proposal: schema variables
Date
Msg-id CAFj8pRA_jZYuTRHEMsv8CnZLBqmnS5xRjcZh-uf0nBWA7WrzMA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] proposal: schema variables  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] proposal: schema variables
Re: [HACKERS] proposal: schema variables
List pgsql-hackers
Hi

2018-08-11 20:46 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:


2018-08-11 7:39 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.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

pgsql-hackers by date:

Previous
From: Edmund Horner
Date:
Subject: Tid scan improvements
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] Optional message to user when terminating/cancelling backend