Skip site navigation (1) Skip section navigation (2)

pg_dumpall size twist

From: Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: pg_dumpall size twist
Date: 2008-10-21 18:37:06
Message-ID: B0D7C0A3F35FE144A70312D086CBCA9B020A822A50@ExchMailbox2.univ.dir.wwu.edu (view raw or flat)
Thread:
Lists: pgsql-admin
I submitted a post about my pg_dumpall file being twice as big on one server compared to the other.
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?
I read in the documentation to start the restore with a starting point, and that postgres is a good place to start.

Marc

Responses

pgsql-admin by date

Next:From: Scott WhitneyDate: 2008-10-21 20:02:39
Subject: PITR question with base backup
Previous:From: Guillaume LelargeDate: 2008-10-21 18:26:37
Subject: Re: oid2name

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group