Re: new --maintenance-db options

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new --maintenance-db options
Date: 2012-06-23 23:28:29
Message-ID: CA+OCxoyA_mRH-HiocD4-QxFR=uRR0zE-EX399g3WosHD0pBU7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Saturday, June 23, 2012, Peter Eisentraut wrote:

> About the new --maintenance-db options:
>
> Why was this option not added to createuser and dropuser? In the
> original discussion[0] they were mentioned, but it apparently never made
> it into the code.
>
> I find the name to be unfortunate. For example, I think of running
> vacuum as "maintenance". So running vacuumdb --maintenance-db=X would
> imply that the vacuum maintenance is done on X. In fact, the whole
> point of this option is to find out where the maintenance is to be run,
> not to run the maintenance. Maybe something like --initial-db would be
> better?
>

I'm not saying it's the best name, but I suspect the origin is pgAdmin
which has used 'Maintenance DB' for 10+ years. There's likely a certain
amount of familiarity with the term amonst pgAdmin users.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-06-23 23:44:36 Re: pg_dump and dependencies and --section ... it's a mess
Previous Message Kevin Grittner 2012-06-23 22:38:10 Re: foreign key locks