| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is citext/regress failing on hamerkop? |
| Date: | 2024-05-15 06:00:00 |
| Message-ID: | de1bac35-3be4-7380-8129-7fb5689f6009@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-05-15 06:13:23 | Re: SQL:2011 application time |
| Previous Message | Masahiko Sawada | 2024-05-15 05:56:54 | Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation |