Обсуждение: [PATCH] Update README for Resource Owners

Hasn't been updated as built-in support grew for temp files, DSM segments,
and JIT contexts.

With enough luck, a README update won't break anything.

-Chap

Hi,

On 2018-04-06 19:46:25 -0400, Chapman Flack wrote:
> Hasn't been updated as built-in support grew for temp files, DSM segments,
> and JIT contexts.
> 
> With enough luck, a README update won't break anything.

Wouldn't it be a better idea not to have a list there, that's guaranteed
to get out of date?

Greetings,

Andres Freund

On 04/06/18 19:52, Andres Freund wrote:
> On 2018-04-06 19:46:25 -0400, Chapman Flack wrote:
>> Hasn't been updated as built-in support grew for temp files, DSM segments,
>> and JIT contexts.
>>
>> With enough luck, a README update won't break anything.
> 
> Wouldn't it be a better idea not to have a list there, that's guaranteed
> to get out of date?

That might look like this, then.

But I'm not sure how bad it is to have a list. How often does ResourceOwner
get taught a new type? It took nine years to grow these last three.

-Chap

On 04/06/18 20:19, Chapman Flack wrote:
> On 04/06/18 19:52, Andres Freund wrote:
>> Wouldn't it be a better idea not to have a list there, that's guaranteed
>> to get out of date?
> 
> That might look like this, then.
> 
> But I'm not sure how bad it is to have a list. How often does ResourceOwner
> get taught a new type? It took nine years to grow these last three.

It also seemed worth documenting that the release callbacks are called
for *every* ResourceOwnerRelease, but can consult CurrentResourceOwner to
learn what owner is really being released.

-Chap