From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | resowner module README needs update? |
Date: | 2021-09-13 13:44:11 |
Message-ID: | CA+HiwqHtfT9z=4H5+F7DOy0OyNHAaVwuRcakt9b2t2uADOaiag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I was reading src/backend/utils/resowner/README today and noticed the
following paragraph that mentions the types of objects/resources
*directly* supported by the module.
===
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.
===
It seems a bunch of other object/resource types have been integrated
into the resowner mechanism since the list was last updated (2008).
Attached patch updates the list. Not sure though if we should keep
the current format of the list, which after updating becomes a bit too
long.
--
Amit Langote
EDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
update-resowner-readme.patch | application/octet-stream | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Private Information Retrieval(PIR) | 2021-09-13 14:45:30 | Re: Private Information Retrieval (PIR) as a C/C++ Aggregate Extension |
Previous Message | tanghy.fnst@fujitsu.com | 2021-09-13 13:36:03 | RE: Added schema level support for publication. |