| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | new --maintenance-db options |
| Date: | 2012-06-23 22:26:58 |
| Message-ID: | 1340490418.14881.14.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
What is the purpose of these options? The initial discussion was
unclear on this. The documentation contains no explanation of why they
should be used. If we want to really support the case where both
postgres and template1 are removed, an environment variable might be
more useful than requiring this to be typed out for every command.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-06-23 22:38:10 | Re: foreign key locks |
| Previous Message | Dean Rasheed | 2012-06-23 22:08:31 | Re: CREATE FOREGIN TABLE LACUNA |