[PATCH] Update README for Resource Owners

Started by Chapman Flackabout 8 years ago4 messageshackers
Jump to latest
#1Chapman Flack
chap@anastigmatix.net

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

Attachments:

0001-Update-README-for-Resource-Owners.patchtext/x-patch; name=0001-Update-README-for-Resource-Owners.patchDownload+7-7
#2Andres Freund
andres@anarazel.de
In reply to: Chapman Flack (#1)
Re: [PATCH] Update README for Resource Owners

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

#3Chapman Flack
chap@anastigmatix.net
In reply to: Andres Freund (#2)
Re: [PATCH] Update README for Resource Owners

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

Attachments:

0001-Update-README-for-Resource-Owners-v2.patchtext/x-patch; name=0001-Update-README-for-Resource-Owners-v2.patchDownload+10-7
#4Chapman Flack
chap@anastigmatix.net
In reply to: Chapman Flack (#3)
Re: [PATCH] Update README for Resource Owners

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

Attachments:

0001-Update-README-for-Resource-Owners-v3.patchtext/x-patch; name=0001-Update-README-for-Resource-Owners-v3.patchDownload+14-7