From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
Cc: | d(dot)kovalenko(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) |
Date: | 2025-09-03 14:48:17 |
Message-ID: | 803146.1756910897@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-09-03 14:57:53 | Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore |
Previous Message | Dilip Kumar | 2025-09-03 12:45:13 | Re: BUG #19041: Logical replication locks wal processing |