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 1lROea-0002Kh-Sr for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Mar 2021 00:24:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lROeY-00035T-KC for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Mar 2021 00:24:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lROeX-00030o-KS for pgsql-hackers@lists.postgresql.org; Wed, 31 Mar 2021 00:24:10 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lROeV-00015O-51 for pgsql-hackers@lists.postgresql.org; Wed, 31 Mar 2021 00:24:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id EF5392092; Tue, 30 Mar 2021 20:24:04 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 30 Mar 2021 20:24:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=nUXEoPuqh/HbyYa/YqKt+lrAPwlBk5KdIReaL0SQLqw=; b=a9HFZbwS bIhBnKakuRC8AakdBA1obYNgEWK5RgiO4IjLWXDOBS/LTBGgHmWvNeXtDGs1VwHU XDQGG1+fxQ+oBHfkDkGkqW2YZJfRDTLnXqMc7TTzbMbh5H4TxF/wti0baOgCE6f9 wK/Yg0trEj2TtH9ow1XlZJldzxHx38wv5No+ux/EBz1XfLzxbLkn8qbyTHfohRtd L7MPJIe7pvcvgNqzU1ktIft9WzfAyHFVgg9K2HMVoDwpzBLQKnfb+Ecgjwv7GT/g c7ea4WkrojS+E9iLfulkXtQtXpdqj9Xmk+V8DiSAb4k1LSQ/NIGyLQcAaH7gBYbs oFaUBlcrjMS5YA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeiuddgfeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoteeftdelqddtudculddvtddmnecujfgurhepff fhvffukfggtggugfgjfgesthekredttderudenucfhrhhomhepfddkrghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrghdkfdcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnoh dqihhprdhorhhgqeenucggtffrrghtthgvrhhnpeegheeludetkeeuueekfedukeetueff iefhieelkeeukeethfduvdejjefgffeuvdenucffohhmrghinhepphhgshhqlhdrsghuih hlugdpphhoshhtghhrvghsqhhlrdhorhhgnecukfhppeduledtrdelhedrudelrdelheen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhh gvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id A1CC3108006C; Tue, 30 Mar 2021 20:24:03 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id EF21D2A0A6F; Tue, 30 Mar 2021 21:24:00 -0300 (-03) Date: Tue, 30 Mar 2021 21:24:00 -0300 From: "'alvherre@alvh.no-ip.org'" To: "iwata.aya@fujitsu.com" Cc: "tsunakawa.takay@fujitsu.com" , 'Kyotaro Horiguchi' , "tgl@sss.pgh.pa.us" , "k.jamison@fujitsu.com" , "pgsql-hackers@lists.postgresql.org" Subject: Re: libpq debug log Message-ID: <20210331002400.GA21316@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210330235255.GA17949@alvherre.pgsql> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk So crake failed. The failure is that it doesn't print the DataRow messages. That's quite odd. We see this in the trace log: Mar 30 20:05:15 # F 54 Parse "" "SELECT 1.0/g FROM generate_series(3, -1, -1) g" 0 Mar 30 20:05:15 # F 12 Bind "" "" 0 0 0 Mar 30 20:05:15 # F 6 Describe P "" Mar 30 20:05:15 # F 9 Execute "" 0 Mar 30 20:05:15 # F 4 Sync Mar 30 20:05:15 # B 4 ParseComplete Mar 30 20:05:15 # B 4 BindComplete Mar 30 20:05:15 # B 33 RowDescription 1 "?column?" NNNN 0 NNNN 65535 -1 0 Mar 30 20:05:15 # B 70 ErrorResponse S "ERROR" V "ERROR" C "22012" M "division by zero" F "SSSS" L "SSSS" R "SSSS" \\x00 Mar 30 20:05:15 # B 5 ReadyForQuery I and the expected is this: Mar 30 20:05:15 # F 54 Parse "" "SELECT 1.0/g FROM generate_series(3, -1, -1) g" 0 Mar 30 20:05:15 # F 12 Bind "" "" 0 0 0 Mar 30 20:05:15 # F 6 Describe P "" Mar 30 20:05:15 # F 9 Execute "" 0 Mar 30 20:05:15 # F 4 Sync Mar 30 20:05:15 # B 4 ParseComplete Mar 30 20:05:15 # B 4 BindComplete Mar 30 20:05:15 # B 33 RowDescription 1 "?column?" NNNN 0 NNNN 65535 -1 0 Mar 30 20:05:15 # B 32 DataRow 1 22 '0.33333333333333333333' Mar 30 20:05:15 # B 32 DataRow 1 22 '0.50000000000000000000' Mar 30 20:05:15 # B 32 DataRow 1 22 '1.00000000000000000000' Mar 30 20:05:15 # B 70 ErrorResponse S "ERROR" V "ERROR" C "22012" M "division by zero" F "SSSS" L "SSSS" R "SSSS" \\x00 Mar 30 20:05:15 # B 5 ReadyForQuery I ... I wonder if this is a libpq pipeline problem rather than a PQtrace problem. In that test case we're using the libpq singlerow mode, so we should see three rows before the error is sent, but for some reason crake is not doing that. aborted pipeline... NOTICE: table "pq_pipeline_demo" does not exist, skipping ok got expected ERROR: cannot insert multiple commands into a prepared statement got expected division-by-zero ok 5 - libpq_pipeline pipeline_abort not ok 6 - pipeline_abort trace match Other hosts seem to get it right: # Running: libpq_pipeline -t /Users/buildfarm/bf-data/HEAD/pgsql.build/src/test/modules/libpq_pipeline/tmp_check/log/pipeline_abort.trace pipeline_abort port=49797 host=/var/folders/md/8mp8j5m5169ccgy11plb4w_80000gp/T/iA9YP9_IHa dbname='postgres' 10000 aborted pipeline... NOTICE: table "pq_pipeline_demo" does not exist, skipping ok got expected ERROR: cannot insert multiple commands into a prepared statement got row: 0.33333333333333333333 got row: 0.50000000000000000000 got row: 1.00000000000000000000 got expected division-by-zero ok 5 - libpq_pipeline pipeline_abort ok 6 - pipeline_abort trace match -- Álvaro Herrera Valdivia, Chile "This is what I like so much about PostgreSQL. Most of the surprises are of the "oh wow! That's cool" Not the "oh shit!" kind. :)" Scott Marlowe, http://archives.postgresql.org/pgsql-admin/2008-10/msg00152.php