Thom Brown wrote:
> On 15 March 2011 15:51, Thom Brown <thom@linux.com> wrote:
> > On 15 March 2011 15:37, Bruce Momjian <bruce@momjian.us> wrote:
> >> Thom Brown wrote:
> >>> On 15 March 2011 15:26, Bruce Momjian <bruce@momjian.us> wrote:
> >>> >
> >>> > Applied. ?I did not bump the catalog version because they are just
> >>> > comments. ?I assume that is the right procedure.
> >>>
> >>> *SNIP*
> >>>
> >>> >> + ? ? ? ? ? ? "COMMENT ON DATABASE postgres IS 'default administrative connection database';\n",
> >>>
> >>> Default administrative connection database? ?Where's the "connection"
> >>> bit come from?
> >>
> >> There was discussion that 'postgres' is the database that is used for
> >> performing administrative connections, e.g. createdb. ?Yeah, kind of
> >> odd, but that's what it is used for.
> >
> > Hmm... there's actually no mention of that in the docs for such tools:
> > http://www.postgresql.org/docs/9.0/static/app-createdb.html
> >
> > There's also little mention of this "administrative" database in the
> > docs beyond saying it's merely a copy of template1 used as a default
> > database for users and applications to connect to.
> >
> > I also notice there's no choice but to use the "postgres" database
> > with these tools. ?Shouldn't we have an option that allows us to
> > specify an alternative database?
> >
> > e.g.
> >
> > createdb -d alternativedb newdb
>
> And example patch attached.
We have actually never gotten a request for this so it is hard to see
why we would add it.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +
