Re: [PATCHES] default database creation with initdb

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] default database creation with initdb
Date: 2005-06-21 08:01:21
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E5CC@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Christopher Kings-Lynne [mailto:chriskl(at)familyhealth(dot)com(dot)au]
> Sent: 21 June 2005 08:57
> To: Dave Page
> Cc: Robert Treat; Tom Lane; Andrew Dunstan; Andreas Pflug;
> Magnus Hagander; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] [PATCHES] default database creation with initdb
>
> > Yes - that's intentional so that pgAdmin/phpPgAdmin et al. can
> > reasonably expect it to be there.
>
> Problem is, how the hell do I know it's there before I connect?

Well obviously you don't (any more than you know that template1 is
accessible until you try), but in time it will be on more and more
systems as people upgrade by when it will make a reasonable default for
clients.

Alternatively, try to connect to it first, and then fall back to
template1 (much as libpq negotiates protocol versions with the server).

Regards, Dave

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2005-06-21 08:16:21 Re: [PATCHES] default database creation with initdb
Previous Message Christopher Kings-Lynne 2005-06-21 07:57:04 Re: [PATCHES] default database creation with initdb