Re: [PATCHES] default database creation with initdb

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

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 20 June 2005 14:19
> To: Andrew Dunstan
> Cc: Dave Page; Andreas Pflug; Robert Treat; Magnus Hagander;
> pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] [PATCHES] default database creation
> with initdb
>
> I don't see that much of a problem with having createdb etc. hardwire
> postgres instead of template1 as the db-to-connect-to.

OK, new patch posted to -patches that updates all the utilities as well.

The only change I didn't make was in line 3458 (in StartChildProcess) of
postmaster.c - template1 seemed the more sensible option to leave there.
Let me know if you disagree and I'll change it :-)

Regards, Dave.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lee Harr 2005-06-20 17:23:18 Re: plpgsql constraint checked data fails to restore
Previous Message Tom Lane 2005-06-20 14:48:07 Re: [PATCHES] default database creation with initdb