Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nBnSj-0004CQ-22 for pgsql-novice@arkaria.postgresql.org; Mon, 24 Jan 2022 00:44:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nBnSh-0006fK-C0 for pgsql-novice@arkaria.postgresql.org; Mon, 24 Jan 2022 00:43:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nBnSh-0006fB-1F for pgsql-novice@lists.postgresql.org; Mon, 24 Jan 2022 00:43:59 +0000 Received: from mail-il1-x134.google.com ([2607:f8b0:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nBnSe-0006fS-Jq for pgsql-novice@lists.postgresql.org; Mon, 24 Jan 2022 00:43:58 +0000 Received: by mail-il1-x134.google.com with SMTP id v17so12491975ilg.4 for ; Sun, 23 Jan 2022 16:43:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9haoRq/DCJg77NoUx/GplYFz2WZ5b0tSZMP9mhL5LjY=; b=S53V966c14aRHi/ij4K7+n6QPwOdaPTKjvTsLkDlgC+FyRS826fDwaVvmC0n2nz0NL 3c3yZHWeJ/SzDnzA+q3a+fVm3gMygUh6JVlzX1rrPM3ZyIbHc1CZIgy5ynpBMNWOLttq pq+AJ54m1FLfOK10HnZLCvo2vEJ86XELC8OAhnREHsEdobAf8Zt9ecXRSIGd95/PmpXY 5t4KqDOX6Cbo9UtylfEXfQ8G2iqoOozS6dpRXFBzkVMagb7cGHs3sSWBTk8x4khIGsmP 1aA1THj8Y/hwIwEB7U37QsThMNaW8kj0KP7VCvCoj0lrn61oVk20sh6f3Ay/duLUm831 7x7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9haoRq/DCJg77NoUx/GplYFz2WZ5b0tSZMP9mhL5LjY=; b=Dgej3CratHjU/1Ua97XpZ5gjOxlBRyGILlZ8Xbf28wjOsNLoFBIzIGYKoxtY1euRxd IE8IUl1qPTHUeDjT3dMdj31KyhJGkumQmXUiCr8o1LvKLlLz/4cbrNJ79KwLVieRGnJy 8DF9Py+j2VB7JKEgmEn0V2p70UO4vU+VIxiwIaGVL4P1qa6QwotMeKLvgphFDrUeh/0Z UHb8RRvVSJL9ciOhNHdQmImvgOruxlo3nA6p7ON+huwFMyIUq7Y53LMGn134saWQEBnp osMDn0VbcWmWBJscfZNbea/D5JW6/691mBX5MmbprtjGQ1DAm8VGEXD0FqSbEhPkSspO uE6g== X-Gm-Message-State: AOAM531eVjPukD67f8ZyLej/+js/HhsXgJbLThXuFxwzoFGHlqPWpp/8 2hiqKxVdseAd5IfHT1cB2VytASQ9A1MIDldJN5Y= X-Google-Smtp-Source: ABdhPJzDub6g3fFCU5OPZWm2LR09xC0v3vnQ6Yx3BpDviRlo6Xz8Pcf84vrg1qw7hXxA0dwlxKtNLV6T/obxFLVgA7c= X-Received: by 2002:a92:bd09:: with SMTP id c9mr7141254ile.102.1642985034758; Sun, 23 Jan 2022 16:43:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Greg Rychlewski Date: Sun, 23 Jan 2022 19:43:44 -0500 Message-ID: Subject: Re: replication connection and multi-command queries To: "David G. Johnston" Cc: pgsql-novice Content-Type: multipart/alternative; boundary="0000000000005e3ee705d649437f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005e3ee705d649437f Content-Type: text/plain; charset="UTF-8" On Sun, Jan 23, 2022 at 7:37 PM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Sun, Jan 23, 2022 at 5:28 PM David G. Johnston < > david.g.johnston@gmail.com> wrote: > >> On Sun, Jan 23, 2022 at 5:24 PM Greg Rychlewski < >> greg.rychlewski@gmail.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. > Thank you. I will give those lists a shot. Apologies for the top-posting. I think I did it properly this time but gmail is a bit weird. Apologies if this is not inline either. --0000000000005e3ee705d649437f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jan 23, 2022 at 7:37 PM David G. = Johnston <david.g.johnston= @gmail.com> wrote:
On Sun, Jan 23, 2022 at 5:28 PM David G. John= ston <da= vid.g.johnston@gmail.com> wrote:
On Sun, Jan 23, 20= 22 at 5:24 PM Greg Rychlewski <greg.rychlewski@gmail.com> wrote:
Thanks for your reply. To give more context: I= am contributing to a Postgres driver used by a programming language. We ar= e currently trying to understand what is legal/not legal to be sent through= this connection.=C2=A0

In the documentation it states t= hat the simple query protocol is followed on these connections, which is wh= y we assumed a multi-command statement would work. I just wanted to make su= re 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.=C2=A0 The convention on these lists is to inli= ne post.

If you are interac= ting at the protocol layer you probably should be posting to -hackers, not = -novice.


Or a -bug report.=C2=A0 It would be good to show the = code you are using to provoke the error.=C2=A0 But I do see where we docume= nt the Simple Query Protocol and do not qualify it such that it doesn't= take a multi-command message.

David J.

Thank you. I= will give those lists a shot. Apologies for the top-posting. I think I did= it properly this time but gmail is a bit weird. Apologies if this is not i= nline either.
--0000000000005e3ee705d649437f--