From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: session server side variables |
Date: | 2016-12-26 18:37:30 |
Message-ID: | CAFj8pRAuSNT76ViXvPJMLv-dXk2U92hzr=awgnXMiw20UJLjmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2016-12-26 19:13 GMT+01:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
>
>
> 2016-12-26 18:20 GMT+01:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:
>
>>
>>
>>
>> And how would it interact with some "fully persistent/shared" variables?
>>
>>
>>
>> I have not any use case for this. I don't know about any similar feature
>> in other database systems. Oracle uses dbms_pipe or dbms_alert for
>> interprocess communication.
>>
>> I am thinking so it is possible to implement. If it is not ACID, then it
>> can work as custom statistic counters. If it should be ACID? Then is better
>> to use table. What I know, now is preferred share nothing design in
>> parallel systems - so for me, it looks like little bit dangerous feature -
>> and I see only one use case - custom statistics - where possible race
>> condition is not hard issue.
>>
>> But I don't plan to implement it in first stage. There should be strong
>> use case for implementing any complex feature in shared memory. But any
>> implementation doesn't breaking to implement it in feature.
>>
>
for custom statistic some extension based on bg worker can be better -
sharing variables are risk of race conditions - and developers are people
only.
I have not a clean opinion about this - the implementation should not be
hard, but I am not sure if this gun I would to give to users.
Regards
Pavel
>
>> Regards
>>
>> Pavel
>>
>>
>> --
>> Fabien.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-26 19:04:22 | Re: propose to pushdown qual into EXCEPT |
Previous Message | Alvaro Herrera | 2016-12-26 18:36:47 | Re: Incautious handling of overlength identifiers |