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 1uHcvA-0067TS-Tv for pgsql-hackers@arkaria.postgresql.org; Wed, 21 May 2025 06:27:20 +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 1uHcv9-003Xli-G1 for pgsql-hackers@arkaria.postgresql.org; Wed, 21 May 2025 06:27:19 +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 1uHcv9-003XlE-5H for pgsql-hackers@lists.postgresql.org; Wed, 21 May 2025 06:27:19 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uHcv6-0005el-2Z for pgsql-hackers@lists.postgresql.org; Wed, 21 May 2025 06:27:17 +0000 Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-acbb85ce788so1258421966b.3 for ; Tue, 20 May 2025 23:27:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1747808835; x=1748413635; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=ZGCYEGhgrUt4aliGjR83H46V9PPxIcJLR0XVAkJydoI=; b=rTRAyfnTcsULuwTOXLQRW+oUXglT6NK1Q3Sj0Ley5vgE6WX40ksqRj3a//oIXDJjFJ 30spauQvyG8Y2gsp1w3srXaArsIsPmBZKZ4SLsEezLte3kYW4BGRO1JBqWnyfWY5q/wx SUGDtzxfZfUmmKjPpe4P+vFvGhpNMbc3Nd98nzsajGGyxSNB1I3+QJbvp/wVohSmiZ7t Vhk9dx7plfn+a8GWbH+sX9QB9VxpEbj8stNZ68Xk4UC+ttX51pYou78wN31eblarQfGX tk334A1UDSGxrBO1WUyfKahjr9YQiwdYAS+osxwOTY6+QtD7RO4hA+eV7b3L/BlYZC57 t4Sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747808835; x=1748413635; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZGCYEGhgrUt4aliGjR83H46V9PPxIcJLR0XVAkJydoI=; b=oA2s2PsBPOQE22EKkbrib6O7t5Q9IwMVL3XXAuMd0PwvBSkNK1YPfKOiJ5p2BQ30p/ q1WqNyCTipELifAzd0lstF6RVKsI4u05UUKJlDhNHwrOFZQIqYrKLeI0yhmpdgO+RM+5 XscewIzFXRk+YtkRicC0mNA30VHalTU2nyOOYtp15DcO8yxcUhsyp7Z2fl/LK1e+IRTm D1dPfLSOVT4bH28kZCG1eHTQGJBrDOQo/1l2pWOHdvPyxQGz4Po++E+wldayUmiG7duz dOJaRKKZ9cbLKF85PjLbvJ4AWGOprfbhoejXHbjVNK4ebkCakKMVjldqcJQldJTG2yQI jhrQ== X-Forwarded-Encrypted: i=1; AJvYcCWvQbA6+hA18c64qMZZnCQa/8IkLDZM9+SIpCN1dF1FsjDxUbo8zj+NXsV0fa8cGU3dSSNRxBSkHhIv48fk@lists.postgresql.org X-Gm-Message-State: AOJu0YyoxKDGly+LAGeIWomzLh6aTBRHcRa3A3sXcGqAzdGyS99mXQv4 VYffP2jxeuO3/J04zr6IocR3YMu+Gj/H3lnt71uFge1OSS7L8mbTFKfj8wRLBlKd3V8= X-Gm-Gg: ASbGnct5U9xxXcv0MmR7WP4pbn1Qp2q+ata+IcqmrpSSLGf+0a0j82CoKz8bgJeqkuH ey51bSSXnCSzx8GXeRXWKUwsaTnla1NCkhKGx9p20zIZf3ErAag0+lXDoMIOtIQNQYETzgKnIYa 8NFEhhd36ziGuoV0ZSo3Q7sEW6jbXJsCIczjeDHIr6FWf7SZZCCtO+6QRU4qKOCkpYSAV2hogBH 5qgKfULY4WuEyowKh8NHkKtqJOo75tVxRE6tdRWs01iqi5zQFasGwOtNjMRc2yl6GO+s5R0l3Ni vFbT26AqUOWvtgBVC5SWb4SBP5wFip547spH4SFwyqhSqwPRnZaGj9VqAgDqY+d+yTJZWbYArlz IeXa+Sm7ttgg= X-Google-Smtp-Source: AGHT+IEFzTGQQP5r/LGIqCpSqJ95LdjWfS2XbeeZ6Rb3ipkdLQ4xSCOgUnL7g6ZW6DpK76fGShVdsg== X-Received: by 2002:a17:907:7f29:b0:ad5:6b8a:a0a5 with SMTP id a640c23a62f3a-ad56b8aa6abmr1076228766b.56.1747808835575; Tue, 20 May 2025 23:27:15 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([41.66.98.31]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ad52d4cc5dbsm845951466b.169.2025.05.20.23.27.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 May 2025 23:27:15 -0700 (PDT) Message-ID: <7847377f86ea938f4dec068e43eb77a6d0bfc520.camel@cybertec.at> Subject: Re: proposal: schema variables From: Laurenz Albe To: Bruce Momjian Cc: Daniel Gustafsson , Marcos Pegoraro , Pavel Stehule , jian he , Dmitry Dolgov <9erthalion6@gmail.com>, Erik Rijkers , Michael Paquier , Amit Kapila , DUVAL REMI , PostgreSQL Hackers Date: Wed, 21 May 2025 08:27:13 +0200 In-Reply-To: References: <41D2EE98-224D-4B43-9F8B-127525A99CD7@yesql.se> <138d50cd8d9617469922eb0017956a3610089064.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.1 (3.56.1-1.fc42) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2025-05-20 at 17:06 -0400, Bruce Momjian wrote: > f 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. >=20 > Are you saying I should not complain until we have officially rejected > the patch set?=C2=A0 If we officially reject it, the patch author would n= o > longer post it? No, you are free to complain, just as Pavel is free to keep his patch set from rotting. What I am trying to say is that rejecting the patch set is the most effective way to complain. The current state is that Pavel keeps the patch set alive, and occasionally people review it or parts of it. But no committer is accepting or rejectin= g it, so the patch set remains in limbo. This annoys you, and it is certainl= y not a happy experience for the author. Rejection is not nice, but at least it would make it easier for Pavel to move on and spend his energy elsewhere= . Yours, Laurenz Albe