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 1tGLSe-002OyK-80 for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Nov 2024 17:04: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 1tGLSc-00H1DG-L7 for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Nov 2024 17:04:18 +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 1tGLQQ-00Gx74-4y for pgsql-hackers@lists.postgresql.org; Wed, 27 Nov 2024 17:02:02 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tGLQN-004ByB-CL for pgsql-hackers@lists.postgresql.org; Wed, 27 Nov 2024 17:02:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; 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=aTKqUMB0oEy/95kzwMdBLogOpx/onwTQcZT9aFmQFl4=; b=axonc GJksEs1MI8vq7PczfVI6s8cBTxdig2B6JADVTRZqmaUKxN5bj2nKfE+oifeGL8KMr/wYsfU7YPCAJ kqkvKWLCoMAEXGjpzcPzqRbJjQknejO96z4aEkpoq31P9NRcNtrNKU5AIcFGbxLtfQJS6ItYwsI0F z2JGZdJ6KMVKWNZlQsuGZyxcA3SZX94QNLzu2H/OHRO6aZCDWL6DH26yf7U+gcb106UxdmVSXN90v vH+Fjf80NMg0DAiUuwSOMV6rUbDy7H4YbQJuOdFuL6OpDW90rqMpXnelG+W1+N3mQYoLMeaSqlGdc A9oulcyRYwqpfP5d3xSaGmM0xD/5w==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tGLQE-00GtVI-3D; Wed, 27 Nov 2024 12:01:51 -0500 Date: Wed, 27 Nov 2024 12:01:50 -0500 From: Bruce Momjian To: Tom Lane Cc: Alvaro Herrera , 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 Message-ID: References: <202411271557.gaewckwu64dm@alvherre.pgsql> <1869337.1732725865@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1869337.1732725865@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Nov 27, 2024 at 11:44:25AM -0500, Tom Lane wrote: > 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. Uh, I guess we could do that, but we should emit something like "--analyze-in-stages option ignored". -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?"