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 1uHUB6-0037rx-FW for pgsql-hackers@arkaria.postgresql.org; Tue, 20 May 2025 21:07:12 +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 1uHUB5-00991z-7E for pgsql-hackers@arkaria.postgresql.org; Tue, 20 May 2025 21:07:11 +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 1uHUB4-00991d-To for pgsql-hackers@lists.postgresql.org; Tue, 20 May 2025 21:07:10 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uHUB2-0000RD-1d for pgsql-hackers@lists.postgresql.org; Tue, 20 May 2025 21:07:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=NI1ugYOvpDs5f0mdUUeNB23sTvSiRVvbX9tTXX9VAys=; b=PhmXk B+tW2bVjN1JWG/qkslWSblf1F+tBKGUhFpWhSZ3t3FiLl+nnf1oGs9deFbjxoQveTnd8Tnhw3itZk a6wo9FETgA1H2pojRZpJa5jxtfEB4No3it4ZXBPhGeWH3bOZm0GPNbOb1rBaj/3s4s34OqrrXCnJW IP9mruoc9qO1BT/3L6EaL8j9SbmCvsxdZM2VFYP6ZkuKJi3w7hZ5O+7thaEnIBv3OwiEyPrsnqHOc keSH7KKx61w27AEdCVfSM6+xhUZPLlyy8OeqX2ZQHyYTfXMl6enCKxng7JOOySPTfUgXx5T+VIOID FaHyTDzUXKkJkgHx72GrOQrMVxiNg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1uHUAt-005IrI-18; Tue, 20 May 2025 17:06:59 -0400 Date: Tue, 20 May 2025 17:06:59 -0400 From: Bruce Momjian To: Laurenz Albe Cc: Daniel Gustafsson , Marcos Pegoraro , Pavel Stehule , jian he , Dmitry Dolgov <9erthalion6@gmail.com>, Erik Rijkers , Michael Paquier , Amit Kapila , DUVAL REMI , PostgreSQL Hackers Subject: Re: proposal: schema variables Message-ID: References: <41D2EE98-224D-4B43-9F8B-127525A99CD7@yesql.se> <138d50cd8d9617469922eb0017956a3610089064.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <138d50cd8d9617469922eb0017956a3610089064.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, May 20, 2025 at 10:36:54PM +0200, Laurenz Albe wrote: > On Tue, 2025-05-20 at 16:28 -0400, Bruce Momjian wrote: > > Well, we do have a right, e.g., we would not allow someone to repeatedly > > post patches for a Postgres extension we don't manage, or the jdbc > > driver. I also don't think we would allow someone to continue posting > > patches for a feature we have decided to reject, and I think we have > > decided to reject the patch in in its current form. I think we might > > accept a trimmed-down version, but I don't see the patch moving in that > > direction. > > > > Now, of course, if I am the only one who feels this way, I can suppress > > these emails on my end. > > In my opinion, this patch set is adding something that would be valuable to > have in core. > > If no committer intends to pick it up and commit it, I think the proper > action would be to step up and reject the patch set, not complain about the > insistence of the author. Are you saying I should not complain until we have officially rejected the patch set? If we officially reject it, the patch author would no longer post it? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.