From: Chapman Flack <chap@anastigmatix.net>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: [PATCH] Update README for Resource Owners
Date: Fri, 6 Apr 2018 19:46:25 -0400
Message-ID: <5AC806D1.1090608@anastigmatix.net> (raw)
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.patch (text/x-patch, 1.8K) download
From fb06e17916ad6b445b1cf6361de6a7f2749ea225 Mon Sep 17 00:00:00 2001
From: Chapman Flack <chap@anastigmatix.net>
Date: Fri, 6 Apr 2018 19:41:57 -0400
Subject: [PATCH] Update README for Resource Owners.
Built-in support for three more categories of owned object has accreted
without mention in the README.
---
src/backend/utils/resowner/README | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/src/backend/utils/resowner/README b/src/backend/utils/resowner/READMEindex 2998f6b..b65fdb8 100644--- a/src/backend/utils/resowner/README+++ b/src/backend/utils/resowner/README@@ -61,12 +61,13 @@ ResourceOwner transfers lock ownership to the parent instead of actually
releasing the lock, if isCommit is true.
Currently, ResourceOwners contain direct support for recording ownership of
-buffer pins, lmgr locks, and catcache, relcache, plancache, tupdesc, and-snapshot references. Other objects can be associated with a ResourceOwner by-recording the address of the owning ResourceOwner in such an object. There is-an API for other modules to get control during ResourceOwner release, so that-they can scan their own data structures to find the objects that need to be-deleted.+buffer pins, lmgr locks, and catcache, relcache, plancache, tupdesc, snapshot,+open temporary file, dynamic shared memory segment, and JIT context references.++Other objects can be associated with a ResourceOwner by recording the address+of the owning ResourceOwner in such an object. There is an API for other+modules to get control during ResourceOwner release, so that they can scan+their own data structures to find the objects that need to be deleted.
Whenever we are inside a transaction, the global variable
CurrentResourceOwner shows which resource owner should be assigned
--
2.7.3
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: chap@anastigmatix.net
Subject: Re: [PATCH] Update README for Resource Owners
In-Reply-To: <5AC806D1.1090608@anastigmatix.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox