Thread: destroydb and createdb
Uhhh, I've been doing a heck of a lot of createdb and destroydb 'ing of late..... All of a sudden... When I destroy my database, and recreate it... It still retains some of the tables, indexes and sequences..... Even when I drop the tables, destroy the db, and recreate the db... Those specific tables, indexes and sequences are recreated with the database... Along with the data within those tables. I could only assume that destroydb is not successfully removing the appropriate files from the system.... Where should I look for these files so that I can manually remove them? (or is this a very bad idea?) Thanks heaps.. Tim.
Tim Kane <timk@hotgames.com> writes:
> I've been doing a heck of a lot of createdb and destroydb 'ing of
> late.....
> All of a sudden... When I destroy my database, and recreate it... It
> still retains some of the tables, indexes and sequences.....
> Even when I drop the tables, destroy the db, and recreate the db...
> Those specific tables, indexes and sequences are recreated with the
> database... Along with the data within those tables.
"createdb" actually consists of cloning whatever is in the template1
database (which is why it's called a template). I'll bet you got
confused at some point and created some user tables in template1
instead of where you intended to. Now they get cloned into new user
databases. This behavior is often construed as a feature, since
it does have its uses if you know what you're doing.
If you need to get back to a pristine state, wipe your whole
installation and initdb (after making a pg_dump backup of course!);
or you can try to clean out the cruft in template1.
regards, tom lane
On Wed, Feb 09, 2000 at 06:20:26PM +1100, Tim Kane wrote: > Uhhh, > > I've been doing a heck of a lot of createdb and destroydb 'ing of > late..... > > All of a sudden... When I destroy my database, and recreate it... It > still retains some of the tables, indexes and sequences..... > Drop tables in template database and then recreate your database. Ivo.