| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(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-16 01:32:08 |
| Message-ID: | CA+hUKGJiD+x1UeC2YqCjsfUCdDMhxQ1k2VCE9gQh5DM=rzuj5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 16, 2024 at 10:43 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Any chance you could test this version please Alexander?
Sorry, cancel that. v3 is not good. I assume it fixes the GSSAPI
thing and is superficially better, but it doesn't handle code that
calls twice in a row and ignores the first result (I know that
PostgreSQL does that occasionally in a few places), and it's also
broken if someone gets recv() = 0 (EOF), and then decides to wait
anyway. The only ways I can think of to get full reliable poll()-like
semantics is to do that peek every time, OR the complicated patch
(per-socket-workspace + intercepting recv etc). So I'm back to v2.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-05-16 01:35:12 | Re: [PATCH] Add --syntax to postgres for SQL syntax checking |
| Previous Message | Michael Paquier | 2024-05-16 01:02:54 | Re: query_id, pg_stat_activity, extended query protocol |