Re: Assertion failure in pgbench

2025-08-04 Thread Tatsuo Ishii
> On Fri, Aug 1, 2025 at 8:55 PM Fujii Masao wrote: >> Unless there are any objections, I plan to commit this and >> back-patch to v15. > > I've pushed the patch. Thanks! Thanks. Great! -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp

Re: Assertion failure in pgbench

2025-08-02 Thread Fujii Masao
On Fri, Aug 1, 2025 at 8:55 PM Fujii Masao wrote: > Unless there are any objections, I plan to commit this and > back-patch to v15. I've pushed the patch. Thanks! Regards, -- Fujii Masao

Re: Assertion failure in pgbench

2025-08-01 Thread Fujii Masao
On Fri, Aug 1, 2025 at 9:03 AM Tatsuo Ishii wrote: > > > On Thu, Jul 31, 2025 at 11:03 AM Tatsuo Ishii wrote: > >> > Yes. When an error occurs and an error response message returned from > >> > backend, pgbench will send one more sync message, then sends ROLLBACK > >> > if necessary. I think the

Re: Assertion failure in pgbench

2025-07-31 Thread Tatsuo Ishii
> On Thu, Jul 31, 2025 at 11:03 AM Tatsuo Ishii wrote: >> > Yes. When an error occurs and an error response message returned from >> > backend, pgbench will send one more sync message, then sends ROLLBACK >> > if necessary. I think the code above should be changed to call >> > PQgetResult repeatab

Re: Assertion failure in pgbench

2025-07-31 Thread Fujii Masao
On Thu, Jul 31, 2025 at 11:56 AM Tatsuo Ishii wrote: > > > Hi, Tatsuo. > > Do you understand why there is an assertion error in the immediate shutdown > > case? > > No. I was not able to reproduce the case so far. I would be mistaken here, as I haven't been able to reproduce the issue (i.e., asse

Re: Assertion failure in pgbench

2025-07-31 Thread Fujii Masao
On Thu, Jul 31, 2025 at 11:03 AM Tatsuo Ishii wrote: > > Yes. When an error occurs and an error response message returned from > > backend, pgbench will send one more sync message, then sends ROLLBACK > > if necessary. I think the code above should be changed to call > > PQgetResult repeatably unt

Re: Assertion failure in pgbench

2025-07-30 Thread Tatsuo Ishii
> Hi, Tatsuo. > Do you understand why there is an assertion error in the immediate shutdown > case? No. I was not able to reproduce the case so far. Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp

Re: Assertion failure in pgbench

2025-07-30 Thread Stepan Neretin
On Thu, Jul 31, 2025 at 9:03 AM Tatsuo Ishii wrote: > >> Hi, > >> > >> I encountered the following assertion failure in pgbench on the current > master: > >> > >> Assertion failed: (res == ((void*)0)), function discardUntilSync, > >> file pgbench.c, line 3515. > >> Abort trap: 6 > >> > >>

Re: Assertion failure in pgbench

2025-07-30 Thread Tatsuo Ishii
>> Hi, >> >> I encountered the following assertion failure in pgbench on the current >> master: >> >> Assertion failed: (res == ((void*)0)), function discardUntilSync, >> file pgbench.c, line 3515. >> Abort trap: 6 >> >> >> This can be reliably reproduced with the following steps: >>

Re: Assertion failure in pgbench

2025-07-30 Thread Tatsuo Ishii
> Hi, > > I encountered the following assertion failure in pgbench on the current > master: > > Assertion failed: (res == ((void*)0)), function discardUntilSync, > file pgbench.c, line 3515. > Abort trap: 6 > > > This can be reliably reproduced with the following steps: > > --