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 1pytbe-0001iZ-Eq for pgsql-hackers@arkaria.postgresql.org; Tue, 16 May 2023 12:16:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pytbc-0006Qr-Dm for pgsql-hackers@arkaria.postgresql.org; Tue, 16 May 2023 12:16:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pytbc-0006Qi-3r for pgsql-hackers@lists.postgresql.org; Tue, 16 May 2023 12:16:40 +0000 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pytbY-0008To-Lv for pgsql-hackers@lists.postgresql.org; Tue, 16 May 2023 12:16:39 +0000 Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-4f1fe1208a4so13255767e87.2 for ; Tue, 16 May 2023 05:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684239396; x=1686831396; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=w3OblPDUX4mhrBFoBl6GEBmwppm77334KWNZ8Nwfdno=; b=E7SHwWN187EXENVDv95mrXREv961BFTe4PrkbNTBVzBjajcGLzBt4/sIjCsLmas1vB VlBj7BHBj4cX7sOUV9K3WsOpfZEo6eTTstElriOry8xaw6AyJKsCY2Pd2bvo5hsHnq86 Kbq436jkHPFRCMJnKlsXXwp1bi30VPRVUbxTUAkktsHCRwArfe+HvdzG/LPzOXpB8Vcm 6/CgKjQy7iiOZyf/bDrTSZntK3X9fxtyKr5HU1p8hlIt0SY4LHoxhVkcSCLE4KQHbXMO +8jsjpS49KmShY+nThQ1DA3v190y3HszQyO426lCA7txjfLuKgRrSJDwZZthyJmTm+WV JpIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684239396; x=1686831396; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=w3OblPDUX4mhrBFoBl6GEBmwppm77334KWNZ8Nwfdno=; b=JYbUOb2+b/xN4AZQgANcsrvD4hQ5g3jN0tdL24JbQZWTj20voyFkS0ScYR0wWpVykO 5IFsWjSmflT7FBFyFV2ssgR75s01Rd0vSnhBc0H1QE01IdJCvuhUxgeisuT5RDgGbvWq FMP5lBDZ9Q129HOebhHzqxwK7gmpaW4WHXCIiFipcNilsqlBTLZFczZtnKWYPKLPXmHX 2NlDgMpqah8/l1WPTlai2+vXGdOF92nF4hknyOmsJ8sGcuH3JvjlaRs6Dk00uB5EVpOg OKeFNNhbXenzK4s1+N+wX53wSTqcp9S1pa3Fcx7PhcC0OAMbtI1lr2+fhZvgMdamImc9 otiA== X-Gm-Message-State: AC+VfDwyB3oybn/empYX79axV5oMmNcwsE14x1Xs31+omWAfzITvzxrb H3zQBEW78/H9roq7D41dz4+SU22/cHYHEf6hv3k= X-Google-Smtp-Source: ACHHUZ5PQ00B6YVjZmLeU4xhLI4jMr3rsjKta3j51L8WdKgXwNlfUspsAU1soUKFemg+DCfxSqa1l2fHkqwuiJ6c4YU= X-Received: by 2002:ac2:5208:0:b0:4f1:4f43:c182 with SMTP id a8-20020ac25208000000b004f14f43c182mr6838159lfl.62.1684239395490; Tue, 16 May 2023 05:16:35 -0700 (PDT) MIME-Version: 1.0 References: <20230516085045.tugzp5w6kwenfv3k@alvherre.pgsql> In-Reply-To: <20230516085045.tugzp5w6kwenfv3k@alvherre.pgsql> From: Robert Haas Date: Tue, 16 May 2023 08:16:24 -0400 Message-ID: Subject: Re: cutting down the TODO list thread To: Alvaro Herrera Cc: John Naylor , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, May 16, 2023 at 4:50=E2=80=AFAM Alvaro Herrera wrote: > Hmm, I agree with removing the entry from the TODO list, but why is this > something we Do Not Want? If somebody shows up and do some analysis > that in a certain workload it is beneficial to do this, then I don't > think we should turn them down. Yeah, I think Do Not Want should only be to discourage people from submitting patches for things we know were not going to do, and that unless we think that's going to be a problem, we should just remove items completely. Thanks, John, for working on this, BTW. --=20 Robert Haas EDB: http://www.enterprisedb.com