| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Update README for Resource Owners |
| Date: | 2018-04-07 01:10:59 |
| Message-ID: | 5AC81AA3.6090604@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Update-README-for-Resource-Owners-v3.patch | text/x-patch | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2018-04-07 01:31:51 | Re: [HACKERS] path toward faster partition pruning |
| Previous Message | Andres Freund | 2018-04-07 00:59:28 | Re: Online enabling of checksums |