| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: new --maintenance-db options |
| Date: | 2012-06-29 19:07:41 |
| Message-ID: | 20120629190741.GA13225@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 24, 2012 at 01:26:58AM +0300, Peter Eisentraut wrote:
> About the new --maintenance-db options:
>
> 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.
Yes, I had the same question about the usefulness/purpose of the option,
but was out-voted.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-06-29 19:32:26 | Re: new --maintenance-db options |
| Previous Message | Josh Berkus | 2012-06-29 18:31:59 | Re: Posix Shared Mem patch |