Dave Page wrote:
Whether or not users should write to the default db is another issue altogether, and one that I'd rather not see causing this idea to be rejected or get delayed past freeze.
+1
If 'default' is writeable, then
so what if users use it? It won't stop pgAdmin from working, and it won't stop CREATE DATABASE from working. If we /really/ don't want them looking at what we're writing to the cluster, then we can just as easily agree a standard name for a database with phpPgAdmin and any other interested projects, and all co-exist in that. The first time any of the products is used, it creates the database if required.
We can hide that db from using by declaring it a system db anyway, which would prevent most users from using it.
The important thing is that we have a default database for users to connect to from initdb time, and that it isn't template1.
Jup.
Now, as you (Andreas) already seem to have written the easy part of the patch, are you going to check the rest of the docs & sources for references to template1 (and correct where required), or shall I take some time tomorrow? :-)
There's still the interesting idea of naming that db "postgres", which I'd even prefer over default because it includes the idea of default db since dbname=username is a common assumption in pgsql tools and also indicates "this is not for everybody, but just for me, the admin". I'm fine with any name though. 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). I'm much more concerned about the instrumentation patch which apparently is going to be ignored until after feature freeze again as it was last year for 8.0. Regards, Andreas
Regards, Dave.
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
