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 1tjLsi-008v9D-HQ for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Feb 2025 17:23:08 +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 1tjLsf-002ZTE-K9 for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Feb 2025 17:23:05 +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 1tjLsf-002ZT6-AU for pgsql-hackers@lists.postgresql.org; Sat, 15 Feb 2025 17:23:05 +0000 Received: from mout-p-102.mailbox.org ([2001:67c:2050:0:465::102]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tjLsb-000z33-0r for pgsql-hackers@lists.postgresql.org; Sat, 15 Feb 2025 17:23:03 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4YwG2g33jDz9sdr; Sat, 15 Feb 2025 18:22:51 +0100 (CET) Date: Sat, 15 Feb 2025 18:22:49 +0100 From: Christoph Berg To: Andres Freund Cc: Tom Lane , Justin Pryzby , pgsql-hackers@lists.postgresql.org Subject: Re: pg17.3 PQescapeIdentifier() ignores len Message-ID: References: <3718360.1739473209@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Andres Freund > I think that'd be *really* helpful. Of course that does require somebody > watching and raising an alarm... > > Do you have ongoing package builds for sid or such? What I am doing anyway is to trigger the regression test of each package once a month (randomly distributed over the month so I'm not getting swamped with failures) and then try to keep this page as "green" as possible: https://jengus.postgresql.org/view/Testsuite/ > Are there regular outomated rebuilds that could tell us of such a problem > between the release being stamped and actually made? The current proposal would be to simply build the minor releases from the Monday tarballs, do the extended testing on Tuesday/Wednesday by triggering all tests from that Jenkins page, and hopefully complain before Thursday. There are daily builds of all PG server branches, but 1) there are too many temporary failures so I don't have enough time to chase them 2) these packages are not used as basis for regression testing the other packages https://jengus.postgresql.org/view/Snapshot/ 1) might improve once the networking (hello arm64) and IO (hello s390x) issues of some of the build machines are fixed. 2) might be something we should give a try. Either it works, or it turns out there are too many weird minor-version-skew problems that aren't actual bugs. It would still not catch any last-minute regression from security patches, though. Christoph