From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-18 23:23:04 |
Message-ID: | 42B4ACD8.9060104@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> [ redirected back to hackers, since it seems this is far from a finished
> discussion ]
>
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
>
>>What is the purpose of this database? A generalized, shared resource for tool
>>makers and add-on packages to store information in PostgreSQL, or a working
>>database that is usable (and to be used) out of the box for new users? I
>>really don't think we want the latter... I can see users connecting via psql
>>and then playing around with different add/create type statements. It is all
>>too common a question from newbies... "does postgresql have a default
>>database to get started with?" They'll see this database and begin creating
>>schema and using this as thier main database, and I think we ought to avoid
>>that. If people don't like pg_system, pg_addons seem like a much safer name
>>to go with imho.
>
>
> pg_addons or pg_tools or something like that seems like a fine name *for
> the purpose of a tools-only database* ... but that is only one of the
> issues being tossed around here. To me the much more interesting aspect
> of this is reducing the extent to which template1 is serving multiple
> not-very-compatible purposes. I like the idea of a default database
> because it would eliminate two perennial issues:
> * newbies mistakenly cluttering template1 with junk
> * CREATE DATABASE failing because there are other connections to the
> template database.
>
> To be newbie-friendly, such a default database *should* be writable,
> I think. The whole point is to let people play without having to learn
> how to create a database first. If they clutter it up, so what? They
> can always drop it and recreate it --- there won't be anything at all
> special about it. (Thus, Andreas' desire to have it be considered a
> "system object" seems misplaced to me.)
This contradicts my intention to have users *not* to write to it, but
reserve it for system like stuff. You might take everything that's not
in postgres binary as non-system, but the average user's perception is
different.
Apparently we really need two initdb created databases for all purposes.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-06-18 23:26:47 | Re: Login/logout - Utility Database |
Previous Message | Tom Lane | 2005-06-18 23:16:44 | Re: Post-mortem: final 2PC patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2005-06-19 00:16:38 | Re: TODO Item - Return compressed length of TOAST datatypes |
Previous Message | Tom Lane | 2005-06-18 23:16:44 | Re: Post-mortem: final 2PC patch |