> -----Original Message----- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 20 June 2005 10:14 > To: Tom Lane > Cc: Dave Page; Robert Treat; Magnus Hagander; > pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] [PATCHES] default database creation with initdb > > Tom Lane wrote: > > Andreas Pflug <[EMAIL PROTECTED]> writes: > > > >>Can't tell whether I could find time for reviewing the docs > the next > >>days (more interesting for feature freeze is having fixed the > >>implementation anyway). > > > > > > Of the sixty-odd files that mention template1 in current > CVS, only about > > half are documentation. > > The decision which files should be changed must be taken. > e.g. createdb, > dropdb will use template1 hardcoded. Is it acceptable that > those tools > fail if the "postgres" database isn't present any more?
That's what I'm working on atm, and given Tom's previous comment about small-footprint users not wanting an extra 5/6MB on the size of a new cluster, I'm leaving most things using template1 and mainly just updating docs and examples. 'postgres' can then be dropped with no ill effects other than a return to the old template1 etc. issues. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match