Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
Date
Msg-id 803146.1756910897@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
List pgsql-bugs
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> On 2025-Jun-21, Tom Lane wrote:
>> Here's a shot at improving matters.  I also made an effort
>> at cleaning up memory leaks in libpq_pipeline.c, although
>> that's surely neatnik-ism not anything meaningful.

> Yeah, the code looks much better this way.  I thought it was a bit odd
> that a function called confirm_result_status() would actually consume
> said status.  Would it be better as
>   consume_result_status(PGconn *conn, ExecStatusType expected)
> ?

Hm, I chose that name by analogy to the adjacent
confirm_query_canceled(), which is likewise consuming a result.
I agree that "consume" is a better verb, but then let's rename
confirm_query_canceled as well.

> I think the patch is a clear improvement regardless.

Thanks for reviewing!

            regards, tom lane



pgsql-bugs by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: BUG #19041: Logical replication locks wal processing
Next
From: Tom Lane
Date:
Subject: Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore