Re: Suggestion to add --continue-client-on-abort option to pgbench - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Suggestion to add --continue-client-on-abort option to pgbench
Date
Msg-id CAHGQGwFJGCeSkanLW6uNC7d6kOgSYxZvXDz1Q_nrPJ8BDo-AJQ@mail.gmail.com
Whole thread Raw
In response to Re: Suggestion to add --continue-client-on-abort option to pgbench  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On Fri, Nov 14, 2025 at 4:45 PM Chao Li <li.evan.chao@gmail.com> wrote:
> ```
> +               else if (received_sync && res == NULL)
>                 {
> -                       /*
> -                        * PGRES_PIPELINE_SYNC must be followed by another
> -                        * PGRES_PIPELINE_SYNC or NULL; otherwise, assert failure.
> -                        */
> -                       Assert(res == NULL);
> -
>                         /*
>                          * Reset ongoing sync count to 0 since all PGRES_PIPELINE_SYNC
>                          * results have been discarded.
> @@ -3601,6 +3610,15 @@ discardUntilSync(CState *st)
>                         PQclear(res);
>                         break;
>                 }
> ```
>
> As we now add “res==NULL” to the “else if”, once entering "else if (received_sync && res == NULL)”, res must be NULL,
so"PQclear(res);” should be deleted. 

OK, the PQclear() there is unnecessary, so I removed it in the patch I
posted earlier.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Rename sync_error_count to tbl_sync_error_count in subscription statistics
Next
From: shveta malik
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart