From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marc Fromm <Marc.Fromm@wwu.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_dumpall size twist
Date: Tue, 21 Oct 2008 16:55:42 -0400
Message-ID: <9058.1224622542@sss.pgh.pa.us> (raw)
In-Reply-To: <B0D7C0A3F35FE144A70312D086CBCA9B020A822A50@ExchMailbox2.univ.dir.wwu.edu>
References: <B0D7C0A3F35FE144A70312D086CBCA9B020A822A50@ExchMailbox2.univ.dir.wwu.edu>
Marc Fromm <Marc.Fromm@wwu.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Marc.Fromm@wwu.edu
Subject: Re: pg_dumpall size twist
In-Reply-To: <9058.1224622542@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox