[PATCH] Update README for Resource Owners
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t38511psql -h localhost -U postgresBuilt from patchset v4 (message #4), July 27, 2026 at 08:42 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t38511_4 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t38511_4 && git checkout t38511_4Patchset v4 (message #4) is on t38511_4
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
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
Attachments:
0001-Update-README-for-Resource-Owners-v2.patchtext/x-patch; name=0001-Update-README-for-Resource-Owners-v2.patchDownload+10-7
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