Re: [18] Fix a few issues with the collation cache

2024-12-10 Thread Michael Paquier
On Tue, Dec 10, 2024 at 03:34:50PM -0800, Jeff Davis wrote: > I committed some of the patches and fixed problem #1. > > The way I used ResourceOwners to fix problems #2 and #3 is a bit > awkward. I'm not sure if it's worth the ceremony to try to avoid leaks > during OOM. And other paths that leak

Re: [18] Fix a few issues with the collation cache

2024-12-10 Thread Jeff Davis
On Tue, 2024-12-10 at 15:44 +0900, Michael Paquier wrote: > On Fri, Sep 20, 2024 at 05:28:48PM -0700, Jeff Davis wrote: > > Updated and rebased. > > The patch has been failing to apply for a couple of weeks now.  Could > you rebase please? I committed some of the patches and fixed problem #1. Th

Re: [18] Fix a few issues with the collation cache

2024-12-09 Thread Michael Paquier
On Fri, Sep 20, 2024 at 05:28:48PM -0700, Jeff Davis wrote: > Updated and rebased. The patch has been failing to apply for a couple of weeks now. Could you rebase please? -- Michael signature.asc Description: PGP signature

Re: [18] Fix a few issues with the collation cache

2024-09-20 Thread Jeff Davis
On Wed, 2024-08-14 at 16:30 -0700, Jeff Davis wrote: > On Thu, 2024-08-08 at 12:24 -0700, Jeff Davis wrote: > > The collation cache, which maps collation oids to pg_locale_t > > objects, > > has a few longstanding issues: > > Here's a patch set v2. Updated and rebased. Regards, Jeff Davi

Re: [18] Fix a few issues with the collation cache

2024-08-14 Thread Jeff Davis
On Thu, 2024-08-08 at 12:24 -0700, Jeff Davis wrote: > The collation cache, which maps collation oids to pg_locale_t > objects, > has a few longstanding issues: Here's a patch set v2. I changed it so that the pg_locale_t itself a resource kind, rather than having separate locale_t and UCollator r