Re: Optimizing ResouceOwner to speed up COPY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Optimizing ResouceOwner to speed up COPY
Date
Msg-id 1542634.1760642881@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimizing ResouceOwner to speed up COPY  (Tomas Vondra <tomas@vondra.me>)
Responses Re: Optimizing ResouceOwner to speed up COPY
List pgsql-hackers
Tomas Vondra <tomas@vondra.me> writes:
> On 10/16/25 20:12, Tom Lane wrote:
>> Can you find evidence of this change being helpful for anything
>> except this specific scenario in COPY?

> I went through the ResourceOwnerRemember() calls, looking for other
> cases that might create a lot of duplicates, similar to the tuple
> descriptors, but I haven't found anything obvious. Other resources seem
> to be either naturally unique or limited to very few duplicates.

I was thinking of adding some temporary instrumentation, like
just elog'ing whenever the count goes above 1, and seeing where
you get hits during the regression tests.  I'm prepared to believe
this is worth doing, but it'd be nice to have more examples
in mind.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Optimizing ResouceOwner to speed up COPY
Next
From: Álvaro Herrera
Date:
Subject: Re: using index to speedup add not null constraints to a table