RE: ResourceOwner refactoring

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>

To: 'Heikki Linnakangas' <hlinnaka@iki.fi>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-01-18T07:49:20Z

Lists: pgsql-hackers

Dear Heikki,

I apologize for sending again.

> I will check another ResourceOwnerEnlarge() if I have a time.

I checked all ResourceOwnerEnlarge() types after applying patch 0001.
(searched by "grep -rI ResourceOwnerEnlarge")
No problem was found.

Hayato Kuroda
FUJITSU LIMITED

Commits

Make RelationFlushRelation() work without ResourceOwner during abort
- e6cd85772647 17.0 landed
Fix bug in bulk extending temp relation after failure
- d212957254de 17.0 landed
Add missing PGDLLIMPORT markings
- c6b86eaa55ff 17.0 landed
Add test_dsa module.
- 325f54033e59 17.0 landed
Clear CurrentResourceOwner earlier in CommitTransaction.
- c21e6e2fd48c 17.0 landed
Fix dsa.c with different resource owners.
- a8b330ffb6f7 17.0 landed
Fix bug in the new ResourceOwner implementation.
- 8f4a1ab471e6 17.0 landed
Change pgcrypto to use the new ResourceOwner mechanism.
- cd694f60dc97 17.0 landed
Use a faster hash function in resource owners.
- 954e43564d99 17.0 landed
Make ResourceOwners more easily extensible.
- b8bff07daa85 17.0 landed
Move a few ResourceOwnerEnlarge() calls for safety and clarity.
- b70c2143bbbe 17.0 landed