Re: Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Liam Bowen <liambowen(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)
Date: 2022-01-21 20:42:28
Message-ID: 1278635.1642797748@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Liam Bowen <liambowen(at)gmail(dot)com> writes:
> Hey Tom, this quick patch unfortunately didn't work, but now I'm looking
> into other options.

Yeah. I've concluded that that *is* a bug (and just committed the fix)
but it doesn't explain what you're seeing.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Japin Li 2022-01-22 00:18:14 Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
Previous Message Tom Lane 2022-01-21 17:36:44 Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error