Re: Weird test mixup - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: Weird test mixup
Date
Msg-id D2176882-C5B0-4C58-8C88-F2D6DE346E1D@yandex-team.ru
Whole thread Raw
In response to Re: Weird test mixup  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Weird test mixup
List 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 by date:

Previous
From: David Rowley
Date:
Subject: Re: First draft of PG 17 release notes
Next
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition