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 1s77vX-003ohr-Bz for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 06:15:48 +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 1s77vX-00AH1l-CV for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 06:15:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s77vX-00AH1B-2E for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 06:15:47 +0000 Received: from fout4-smtp.messagingengine.com ([103.168.172.147]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s77vP-000Jhu-O8 for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 06:15:46 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfout.nyi.internal (Postfix) with ESMTP id B81F41380184; Wed, 15 May 2024 02:15:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 15 May 2024 02:15:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm2; t=1715753739; x=1715840139; bh=lMOAnT1ZsbbjA6KJ2dCtN5HW9X3mTDQs kiRnB3KFqCQ=; b=jtJYr+RrOXiEjn1o83VQG7dpy/+JWTovTJaptMZWRy8ztSFZ 3Y9Af4LdLNT5iqOK4yIxDaX3kmrGiESUBTvaA/DkX/xMsp2qerNq7b2DkFwuxwHZ G3YGSq2narTPkFP3BLCher6CF6N1qgcj1Jj8iLTzN5h+PtPi6V1y9zKcMktx+LLj CPcYhH2HNxnrG6HukhtMyGCRuMNXMWTjOWv5IgaFz7lChiFNwMRS4Tx6BqWuE8nG K0P46I7a0z+3vR2DVLY3v8s3Fsp0Ja5L/ZHHCUR+X8+9NVxCE1YBofLVKoCHhlgw vaWrNYmHCfVO7MiE4ZVhMyccwBoHjVnRh/yR0w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715753739; x= 1715840139; bh=lMOAnT1ZsbbjA6KJ2dCtN5HW9X3mTDQskiRnB3KFqCQ=; b=T r6rNzp3D8XomA+yHF+tg/5WfhA8qQAha4b5AgiLBOq0dzhKgvRfi2pMq2TbzlgHF L3bb8i44v8+mddh+2JUO2G1tJoSVsKl8+/owioLQl/BCtYgtZTCqS++gC3ZueNG1 PcXazwhN0Q+zovvMJ5qJQMHS3nV8xdAic/8ABfY+bRMlyddIw4dF1sKqYfasJKpo SgX3DyGRXcllOegvuelCoYpARArrpi/kHAUEkzctphu2rI8SbYzZrXsBd/zer37Y wC1dUOYUqb43EeWPDK9BIvWdGZ5f8z9RfCjvU8JAn3OMqbyGIp8JstE0naQwVUpM rALiTCLQNJTmpv6fmTDZQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegjedguddtudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorh hgqeenucggtffrrghtthgvrhhnpefgjedthfekfedtuefgieelheetleejgefhueeltdfh ueetvdffudekfeejhfegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 May 2024 02:15:38 -0400 (EDT) Message-ID: Date: Wed, 15 May 2024 08:15:37 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence To: Michael Paquier Cc: Alvaro Herrera , pgsql-hackers@lists.postgresql.org, Jacob Champion References: <202405101223.66lahv2qiwe7@alvherre.pgsql> <6dae7e56-5233-4183-bd12-c14cf3c9312e@eisentraut.org> Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 15.05.24 02:00, Michael Paquier wrote: > On Tue, May 14, 2024 at 10:39:36AM +0200, Peter Eisentraut wrote: >> I saw the same thing. The problem is that there is incomplete dependency >> information in the makefiles (not meson) between src/common/ and what is >> using it. So whenever anything changes in src/common/, you pretty much have >> to do a forced rebuild of everything. > > Is that a recent regression? I have some blurry memories from > working on these areas that changing src/common/ reflected on the > compiled pieces effectively at some point. One instance of this problem that I can reproduce at least back to PG12 is 1. touch src/common/exec.c 2. make -C src/bin/pg_dump This will rebuild libpgcommon, but it will not relink pg_dump.