| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com> |
| Cc: | "adrian(dot)klaver(at)gmail(dot)com" <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to remove the current database and populate the database with new data? |
| Date: | 2010-06-04 00:43:02 |
| Message-ID: | 4C084C16.7070006@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/06/2010 7:26 AM, Wang, Mary Y wrote:
> I thought about DROP DATABASE, but wasn't sure if it would clean up EVERYTHING.
It won't remove your users and roles, or anything else that you see
reported in pg_dumpall --globals-only .
> I assume most of you would just do the DROP DATABASE for the scenario that I described. Is that correct?
Yep. I essentially _never_ re-initdb, personally. For one thing, I often
have other databases in a cluster that I'd rather not lose, but it's
also generally unnecessary.
( I do frequently wish for the ability to create roles at the database
rather than cluster level, though, as it'd make cleaning the DB for
testing of schema creation scripts and the like considerably easier. Not
to mention backups. )
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Broersma | 2010-06-04 04:49:00 | Requested addition to the todo list [was]: Re: Altering Domain Constraints on composite types |
| Previous Message | Gareth.Williams | 2010-06-03 23:43:18 | Re: create index concurrently - duplicate index to reduce time without an index |