Re: Weird test mixup
От | Andrey M. Borodin |
---|---|
Тема | Re: Weird test mixup |
Дата | |
Msg-id | D2176882-C5B0-4C58-8C88-F2D6DE346E1D@yandex-team.ru обсуждение исходный текст |
Ответ на | Re: Weird test mixup (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Weird test mixup
|
Список | pgsql-hackers |
> On 10 May 2024, at 06:04, Michael Paquier <michael@paquier.xyz> wrote: > > Attached is an updated patch for now Can you, please, add some more comments regarding purpose of private data? I somewhat lost understanding of the discussion for a week or so. And I hoped to grasp the idea of private_data from resultingcode. But I cannot do so from current patch version... I see that you store condition in private_data. So "private" means that this is a data specific to extension, do I understandit right? As long as I started anyway, I also want to ask some more stupid questions: 1. Where is the border between responsibility of an extension and the core part? I mean can we define in simple words whatfunctionality must be in extension? 2. If we have some concurrency issues, why can't we just protect everything with one giant LWLock\SpinLock. We have somelocking model instead of serializing access from enter until exit. Most probably, this was discussed somewhere, but I could not find it. Thanks! Best regards, Andrey Borodin.
В списке pgsql-hackers по дате отправления: