From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com> |
Cc: | pgsql-novice <pgsql-novice(at)lists(dot)postgresql(dot)org> |
Subject: | Re: replication connection and multi-command queries |
Date: | 2022-01-24 00:37:03 |
Message-ID: | CAKFQuwaE6QhRrSPQoncxM5UtrikykW7Zjkx9RuNjyr7VmB0X2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Sun, Jan 23, 2022 at 5:28 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Sun, Jan 23, 2022 at 5:24 PM Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com>
> wrote:
>
>> Thanks for your reply. To give more context: I am contributing to a
>> Postgres driver used by a programming language. We are currently trying to
>> understand what is legal/not legal to be sent through this connection.
>>
>> In the documentation it states that the simple query protocol is followed
>> on these connections, which is why we assumed a multi-command statement
>> would work. I just wanted to make sure we are not doing anything wrong and
>> that it is disallowed by design. We can, for instance, send "SELECT 1;" and
>> receive a result.
>>
>>>
>>>
> Please don't top-post. The convention on these lists is to inline post.
>
> If you are interacting at the protocol layer you probably should be
> posting to -hackers, not -novice.
>
>
Or a -bug report. It would be good to show the code you are using to
provoke the error. But I do see where we document the Simple Query
Protocol and do not qualify it such that it doesn't take a multi-command
message.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Rychlewski | 2022-01-24 00:43:44 | Re: replication connection and multi-command queries |
Previous Message | David G. Johnston | 2022-01-24 00:28:36 | Re: replication connection and multi-command queries |