pg_dumpall size twist - Mailing list pgsql-admin

From Marc Fromm
Subject pg_dumpall size twist
Date
Msg-id B0D7C0A3F35FE144A70312D086CBCA9B020A822A50@ExchMailbox2.univ.dir.wwu.edu
Whole thread Raw
Responses Re: pg_dumpall size twist  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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

 

pgsql-admin by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: oid2name
Next
From: "Scott Whitney"
Date:
Subject: PITR question with base backup