| From: | Marco Boeringa <marco(at)boeringa(dot)demon(dot)nl> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Thom Brown <thom(at)linux(dot)com> |
| Subject: | Re: Potential "AIO / io workers" inter-worker locking issue in PG18? |
| Date: | 2025-10-10 21:26:38 |
| Message-ID: | a031c5bc-e61e-4ef7-a52c-d6759c97f265@boeringa.demon.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Just found out about the other thread, which seems to describe an issue
that may well be related to the problems I observe in my multi-threaded
Python implementation using PostgreSQL 18:
As I have zero experience compiling PostgreSQL from scratch and
PostgreSQL development in general, I will unfortunately avoid going down
the rabbit hole of such an attempt to be able to test the patch, but
will eagerly await PG18.1 which hopefully will have it included and
might fix the issues I observed.
Marco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-10-10 21:30:20 | Re: Potential "AIO / io workers" inter-worker locking issue in PG18? |
| Previous Message | Zane Duffield | 2025-10-10 20:45:14 | Re: Date/Time parsing of ISO 8601 timestamps with commas |