| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Test database for new installs? |
| Date: | 2004-11-18 21:07:15 |
| Message-ID: | 200411181307.15676.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Folks,
Some issues have come up repeatedly on IRC with new users, enough so that they
might be worth addressing in the code:
a) new users try just to "psql" as postgres, and get a "no such database
postgres";
b) new users use template1 as a testing database, and then have to re-initdb
to clean it up.
Both of these things could be solved by creating an additional, non-template
database called "postgres" at initdb. For security reasons, this db would
be set up in pg_hba.conf as accessable only by postgres via local. It might
not seem like it to experienced programmers, but having a "sandbox" database
which lets you get used to PG commands would be a boon to people how are new
to both Postgres and SQL databases in general.
The only reason not to do it is space; each database takes up about 5mb.
That's nothing to most users but could be a problem for a few. Also, it
would create a minor burden on the fsm to track an extra set of relations.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2004-11-18 21:30:05 | Re: Test database for new installs? |
| Previous Message | G u i d o B a r o s i o | 2004-11-18 20:44:44 | Re: invalid page header |