Re: Statistics Import and Export - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Statistics Import and Export
Date
Msg-id 202411271557.gaewckwu64dm@alvherre.pgsql
Whole thread Raw
In response to Re: Statistics Import and Export  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Statistics Import and Export
Re: Statistics Import and Export
Re: Statistics Import and Export
List pgsql-hackers
On 2024-Nov-27, Bruce Momjian wrote:

> On Wed, Nov 27, 2024 at 09:18:45AM -0600, Nathan Bossart wrote:

> > > Maybe not remove the option, but add a required parameter:
> > > --analyze-in-stages=all / missing
> > > 
> > > That way, if the option is missing, the user can adapt the command line
> > > according to need.
> > 
> > I like this idea.
> 
> 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.

> Uh, do we have parameters that require a boolean option like this? 

I'm not sure what exactly are you asking here.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"La gente vulgar sólo piensa en pasar el tiempo;
el que tiene talento, en aprovecharlo"



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Index AM API cleanup
Next
From: Nathan Bossart
Date:
Subject: Re: Large expressions in indexes can't be stored (non-TOASTable)