Re: Bug in pgbench prepared statements - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Bug in pgbench prepared statements
Date
Msg-id ZWmI3714tv5PGVJ9@paquier.xyz
Whole thread Raw
In response to Re: Bug in pgbench prepared statements  (Lev Kokotov <lev.kokotov@gmail.com>)
Responses Re: Bug in pgbench prepared statements
List pgsql-hackers
On Thu, Nov 30, 2023 at 07:15:54PM -0800, Lev Kokotov wrote:
>> I see prepareCommand() is called one more time in
>> prepareCommandsInPipeline(). Should you also check the return value
>> there?
>
> Yes, good catch. New patch attached.

Agreed that this is not really helpful as it stands

>> It may also be useful to throw this patch on the January commitfest if
>> no one else comes along to review/commit it.
>
> First time contributing, not familiar with the process here, but happy to
> learn.

The patch you have sent does not apply cleanly on the master branch,
could you rebase please?

FWIW, I am a bit confused by the state of sendCommand().  Wouldn't it
better to consume the errors from PQsendQueryPrepared() and
PQsendQueryParams() when these fail?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Peter Eisentraut
Date:
Subject: Remove unnecessary includes of system headers in header files