From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_dumpall size twist |
Date: | 2008-10-21 20:55:42 |
Message-ID: | 9058.1224622542@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu> writes:
> It turns out that one specific database called postgres is growing each time I perform a restore from the pg_dumpall files.
> The database postgres has gone from 5.1MB to 10MB to 15MB to 20MB. No other database is growing like this. The pg_dumpall is using the -c flag to drop databases before restoring them.
> When I do a restore I do this command: psql -U postgres -f alldb postgres.
> Has it something to do with using postgres as the starting db?
Well, yeah: you can't drop the database you're connected to. It might
be a good idea to pay attention to the errors emitted by the dump
script...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-10-22 02:13:44 | Re: PITR question with base backup |
Previous Message | Scott Whitney | 2008-10-21 20:29:52 | Re: PITR question with base backup |