Re: Suggestion to add --continue-client-on-abort option to pgbench
От | Yugo Nagata |
---|---|
Тема | Re: Suggestion to add --continue-client-on-abort option to pgbench |
Дата | |
Msg-id | 20250926102932.617a80a1f2fdd2b221c4d7d4@sraoss.co.jp обсуждение исходный текст |
Ответ на | Re: Suggestion to add --continue-client-on-abort option to pgbench (Fujii Masao <masao.fujii@gmail.com>) |
Список | pgsql-hackers |
On Fri, 26 Sep 2025 00:03:06 +0900 Fujii Masao <masao.fujii@gmail.com> wrote: > On Thu, Sep 25, 2025 at 4:22 PM Yugo Nagata <nagata@sraoss.co.jp> wrote: > > I've attached updated patches. > > Thanks for updating the patches! > > About 0001: you mentioned that the lost error message issue occurs in > pipeline mode. > Just to confirm, are you sure it never happens in non-pipeline mode? > From a quick look, > readCommandResponse() seems to have this problem regardless of whether pipeline > mode is used. > > If it can also happen outside pipeline mode, maybe we should split this from > the assertion failure fix, since they'd need to be backpatched to > different branches. I could not find a code path that resets the error state before reporting in non-pipeline mode, since it is typically reset when starting to send a query. However, referencing an error message after another PQgetResult() does not seem like a good idea in general, so I agree with splitting the patch. I'll submit updated patches soon. Regards, Yugo Nagata -- Yugo Nagata <nagata@sraoss.co.jp>
В списке pgsql-hackers по дате отправления: