| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | emond(dot)papegaaij(at)gmail(dot)com |
| Cc: | pgpool-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: FATAL: simple query "BEGIN" arrived before ending an extended query message |
| Date: | 2025-07-24 06:48:37 |
| Message-ID: | 20250724.154837.765982152313889926.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-general |
> Hi,
>
> There's been some recent development on the side of pgjdbc as well:
> https://github.com/pgjdbc/pgjdbc/pull/3728
>
> We are currently testing that fix. With that patch, pgjdbc will always send
> a sync first when in extended mode before sending a simple query.
Ok. That's good.
> Do you
> think it's still a good idea to support mixing simple and extended mode in
> pgpool? It's difficult for me to assess the risk of your proposed patch.
I agree with your concern. Mixing simple and extended mode is a new
code path in pgpool. Probably mixing simple and extended mode is also
new code path in PostgreSQL backend. We can't ignore both risks.
> Maybe it's better to just not allow it if that makes it easier to implement?
I agree. I withdraw my patch.
> Ps. Sorry for the bad quoting.
No problem at all.
> I'm writing this on my phone, as I'm still
> on vacation.
Sorry for bothering you vacation. Have a nice day!
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 鈴木 涼 | 2025-07-28 07:32:13 | Sudden increase in connections in pgpool usage environment |
| Previous Message | Emond Papegaaij | 2025-07-24 06:04:58 | Re: FATAL: simple query "BEGIN" arrived before ending an extended query message |