Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qSG0N-0053nS-KU for pgsql-bugs@arkaria.postgresql.org; Sat, 05 Aug 2023 12:03:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qSG0L-00FwTu-MN for pgsql-bugs@arkaria.postgresql.org; Sat, 05 Aug 2023 12:03:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qSG0L-00FwTm-8E for pgsql-bugs@lists.postgresql.org; Sat, 05 Aug 2023 12:03:33 +0000 Received: from forward501b.mail.yandex.net ([2a02:6b8:c02:900:1:45:d181:d501]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qSG0H-000fSh-3h for pgsql-bugs@lists.postgresql.org; Sat, 05 Aug 2023 12:03:32 +0000 Received: from mail-nwsmtp-mxback-production-main-146.iva.yp-c.yandex.net (mail-nwsmtp-mxback-production-main-146.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:1c9a:0:640:c9b7:0]) by forward501b.mail.yandex.net (Yandex) with ESMTP id 6F0315EA0C for ; Sat, 5 Aug 2023 15:03:24 +0300 (MSK) Received: from mail.yandex.ru (2a02:6b8:c0c:76a4:0:640:c618:0 [2a02:6b8:c0c:76a4:0:640:c618:0]) by mail-nwsmtp-mxback-production-main-146.iva.yp-c.yandex.net (mxback/Yandex) with HTTP id 83U4302W5qM0-ypgsCEcy; Sat, 05 Aug 2023 15:03:24 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1691237004; bh=vp2RanSysyB9oO5uT54avu1+qF0SasSrOMiRhEFl2/o=; h=Message-Id:Date:Subject:To:From; b=gU2v7Lp/xkFL3ixRrE8uOGfeXlQ//HqcO6//0I4epwCGCkyU8Em4JzhmBWjh1II/K iV/xgwNcQqJ1tL+x+jRgEWEuJaiqQuh0lnQMUEZLG9fy1TCARY+lHKGrgXWRLSi3ZA A8o2vwoBaSMRA5trM6/N98xyJzkdyfF1d5xD+YBs= Authentication-Results: mail-nwsmtp-mxback-production-main-146.iva.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by 6mha55xjikky5vne.iva.yp-c.yandex.net with HTTP; Sat, 05 Aug 2023 15:03:24 +0300 From: =?utf-8?B?0KLRgNC+0YTQuNC80L7QsiDQmNCy0LDQvQ==?= Envelope-From: i-trofimow@yandex.ru To: "pgsql-bugs@lists.postgresql.org" Subject: Re:BUG #17948: libpq seems to misbehave in a pipelining corner case MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 05 Aug 2023 15:03:24 +0300 Message-Id: <82241691236930@mail.yandex.ru> Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk
We've managed to reproduce client <-> server de-synchronization triggered by this, which we are seeing in production.
Libpq considers '< 2TDCEZ' a sufficient response to '> BDESS', when according to specification one more 'Z' is expected.
 
A bit more context and a MRE: https://github.com/itrofimow/libpq_protocol_desync