Re: Wrong usage of pqMsg_Close message code? - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Wrong usage of pqMsg_Close message code?
Date
Msg-id CAJ7c6TPYi5cvMpptYhr+DqBhPcVhciAG-n9kxBro_Q5=NXbY7w@mail.gmail.com
Whole thread Raw
In response to Wrong usage of pqMsg_Close message code?  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Wrong usage of pqMsg_Close message code?
List pgsql-hackers
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

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: psql: show current user in prompt
Next
From: Laurenz Albe
Date:
Subject: Re: Return value of pg_promote()