Re: Why is citext/regress failing on hamerkop? - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Why is citext/regress failing on hamerkop?
Date
Msg-id de1bac35-3be4-7380-8129-7fb5689f6009@gmail.com
Whole thread Raw
In response to Re: Why is citext/regress failing on hamerkop?  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Why is citext/regress failing on hamerkop?
List pgsql-hackers
15.05.2024 01:26, Thomas Munro wrote:
> OK, so we know what the problem is here.  Here is the simplest
> solution I know of for that problem.  I have proposed this in the past
> and received negative feedback because it's a really gross hack.  But
> I don't personally know what else to do about the back-branches (or
> even if that complex solution is the right way forward for master).
> The attached kludge at least has the [de]merit of being a mirror image
> of the kludge that follows it for the "opposite" event.  Does this fix
> it?

Yes, I see that abandoned GSS connections are closed immediately, as
expected. I have also confirmed that `meson test` with the basic
configuration passes on REL_16_STABLE. So from the outside, the fix
looks good to me.

Thank you for working on this!

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
Next
From: Michael Paquier
Date:
Subject: Re: SQL:2011 application time