From: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH v1] PQputCopyEnd never returns 0, fix the inaccurate comment |
Date: | 2023-08-28 13:46:07 |
Message-ID: | CAEG8a3LxhHbOj+8_KDM_v--Lfq2w1KmRDivKF5RhnSs3ZGTgUg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 28, 2023 at 7:48 PM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
>
> Hi Junwang,
>
> > PQputCopyEnd returns 1 or -1, never 0, I guess the comment was
> > copy/paste from PQputCopyData's comment, this should be fixed.
>
> The patch LGTM but I wonder whether we should also change all the
> existing calls of PQputCopyEnd() from:
>
> ```
> PQputCopyEnd(...) <= 0
> ```
>
> ... to:
>
> ```
> PQputCopyEnd(...) < 0
> ```
>
> Given the circumstances, checking for equality to zero seems to be at
> least strange.
>
Yeah, it makes sense to me, or maybe just `PQputCopyEnd(...) == -1`,
let's wait for some other opinions.
>
> On top of that, none of the PQputCopyData() callers cares whether the
> function returns 0 or -1, both are treated the same way. I suspect the
> function does some extra work no one asked to do and no one cares
> about. Perhaps this function should be refactored too for consistency.
>
> Thoughts?
>
> --
> Best regards,
> Aleksander Alekseev
--
Regards
Junwang Zhao
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-08-28 13:46:35 | Commitfest manager for September |
Previous Message | Daniel Gustafsson | 2023-08-28 13:44:49 | Re: Prevent psql \watch from running queries that return no rows |