Re: Wrong usage of pqMsg_Close message code?

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>
To: Aleksander Alekseev <aleksander@timescale.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-08-28T14:01:29Z
Lists: pgsql-hackers

Attachments

Hi

po 28. 8. 2023 v 14:00 odesílatel Aleksander Alekseev <
aleksander@timescale.com> napsal:

> Hi Pavel,
>
> > There is message PqMsgClose, but this should be used from client side.
> Here should be used PqMsg_CommandComplete instead?
>
> It seems so. This change was introduced in f4b54e1ed98 [1]:
>
> ```
> --- a/src/backend/tcop/dest.c
> +++ b/src/backend/tcop/dest.c
> @@ -176,7 +176,7 @@ EndCommand(const QueryCompletion *qc, CommandDest
> dest, bool force_undecorated_o
>
>                         len = BuildQueryCompletionString(completionTag, qc,
>
>                   force_undecorated_output);
> -                       pq_putmessage('C', completionTag, len + 1);
> +                       pq_putmessage(PqMsg_Close, completionTag, len + 1);
>
>                 case DestNone:
>                 case DestDebug
> ```
>
> It should have been PqMsg_CommandComplete.
>
> [1]:
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f4b54e1ed98


here is a patch - all tests passed

Regards

Pavel

>
>
> --
> Best regards,
> Aleksander Alekseev
>

Commits

  1. Fix misuse of PqMsg_Close.