From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: poc - possibility to write window function in PL languages |
Date: | 2021-01-27 09:58:02 |
Message-ID: | CAFj8pRBJf2hQZpA14yPS_Xzd2U9mnWke_ck9NGrY38Dfqkn6kA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
st 20. 1. 2021 v 21:14 odesílatel Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
napsal:
>
>
> st 20. 1. 2021 v 21:07 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>
>> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> > The second question is work with partition context value. This should be
>> > only one value, and of only one but of any type per function. In this
>> case
>> > we cannot use GET statements. I had an idea of enhancing declaration.
>> Some
>> > like
>>
>> > DECLARE
>> > pcx PARTITION CONTEXT (int); -- read partition context
>> > BEGIN
>> > pcx := 10; -- set partition context
>>
>> > What do you think about it?
>>
>> Uh, what? I don't understand what this "partition context" is.
>>
>
> It was my name for an access to window partition local memory -
> WinGetPartitionLocalMemory
>
> We need some interface for this cache
>
I have to think more about declarative syntax. When I try to transform our
WindowObject API directly, then it looks like Cobol. It needs a different
concept to be user friendly.
Regards
Pavel
> Regards
>
> Pavel
>
>
>
>
>
>
>
>>
>> regards, tom lane
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Denis Laxalde | 2021-01-27 10:25:11 | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |
Previous Message | Mark Rofail | 2021-01-27 09:58:01 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |