| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christian Maurer <c(dot)maurer(at)gmx(dot)at> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe |
| Date: | 2024-02-02 18:19:42 |
| Message-ID: | 3222816.1706897982@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Christian Maurer <c(dot)maurer(at)gmx(dot)at> writes:
>> I wondered whether we needed to introduce a critical section
>> to prevent multiple threads from calling that concurrently,
>> even though its docs allege you shouldn't have to. Perhaps
>> it's thread-safe except on Windows?
> This would explain, why I could not reproduce the error on Red Hat Enterprise Linux.
Are you in a position to try a source-code patch? The attached
is very quick-and-dirty, but if it resolves your problem then
we could turn it into something respectable.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| avoid-concurrent-bindtextdomain-calls-wip.patch | text/x-diff | 579 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-02-02 18:39:42 | BUG #18325: Possible bug with plpgsql function + ALTER TABLE DROP COLUMN |
| Previous Message | Christian Maurer | 2024-02-02 16:27:24 | Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe |