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 1tGL9Y-002Mdg-Qb for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Nov 2024 16:44:36 +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 1tGL9X-00Gljb-F0 for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Nov 2024 16:44:35 +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 1tGL9X-00GljT-50 for pgsql-hackers@lists.postgresql.org; Wed, 27 Nov 2024 16:44:35 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tGL9U-004BnR-5t for pgsql-hackers@lists.postgresql.org; Wed, 27 Nov 2024 16:44:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4ARGiPwu1869338; Wed, 27 Nov 2024 11:44:25 -0500 From: Tom Lane To: Alvaro Herrera cc: Bruce Momjian , Nathan Bossart , Magnus Hagander , Corey Huinker , Jeff Davis , jian he , Matthias van de Meent , Stephen Frost , Ashutosh Bapat , Peter Smith , PostgreSQL Hackers Subject: Re: Statistics Import and Export In-reply-to: <202411271557.gaewckwu64dm@alvherre.pgsql> References: <202411271557.gaewckwu64dm@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 27 Nov 2024 16:57:35 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1869336.1732725865.1@sss.pgh.pa.us> Date: Wed, 27 Nov 2024 11:44:25 -0500 Message-ID: <1869337.1732725865@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > On 2024-Nov-27, Bruce Momjian wrote: >> Would there be a default? > There would be no default. Running with no option given would raise an > error. The point is: you want to break scripts currently running > --analyze-in-stages so that they can make a choice of which of these two > modes to run. Your proposal (as I understand it) is to remove the > --analyze-in-stages option and add two other options. My proposal is to > keep --analyze-in-stages, but require it to have a specifier of which > mode to run. Both achieve what you want, but I think mine achieves it > in a cleaner way. I do not like the idea of breaking existing upgrade scripts, especially not by requiring them to use a parameter that older vacuumdb versions will reject. That makes it impossible to have a script that is version independent. I really doubt that there is any usability improvement to be had here that's worth that. How about causing "--analyze-in-stages" (as currently spelled) to be a no-op? We could keep the behavior available under some other name. regards, tom lane