pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: olivier.boissard@cerene.fr <olivier.boissard@cerene.fr>
To: arnaulist@andromeiberica.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Suggestions needed about how to dump/restore a database
Date: Thu, 21 Dec 2006 20:56:45 +0100
Message-ID: <458AE6FD.2010004@cerene.fr> (raw)
In-Reply-To: <458AB4AA.7000902@andromeiberica.com>
References: <45881D1A.6090904@andromeiberica.com>
	<458AB4AA.7000902@andromeiberica.com>

Arnau a écrit :
> Hi all,
>
>>   I've got a DB in production that is bigger than 2GB that dumping it
>> takes more than 12 hours. I have a new server to replace this old one
>> where I have restore the DB's dump. The problem is I can't afford to
>> have the server out of business for so long, so I need your advice about
>> how you'd do this dump/restore. The big amount of data is placed in two
>> tables (statistics data), so I was thinking in dump/restore all except
>> this two tables and once the server is running again I'd dump/restore
>> this data. The problem is I don't know how exactly do this.
>>
>>   Any suggestion?
>>
>> Thanks
>
>   Jeff answer made me check what were the configuration parameters. 
> That machine had the default ones, so I tweaked a bit them and now I 
> got a dump in about 2 hours. To dump the DB I'm using the following 
> command:
>
> /usr/bin/pg_dump -o -b -Fc $db > $backup_file
>
>   And as result I got a file of 2.2GB. The improvement has been quite 
> big but still very far from the 10-15 minutes that Jeff says or the 
> Thomas'3 minutes.
>
>   The version I'm running is a 7.4.2 and the postgresql.conf 
> parameters are the following:
>
> # - Memory -
>
> shared_buffers = 10000          # min 16, at least max_connections*2, 
> 8KB each
> sort_mem = 10240                # min 64, size in KB
> vacuum_mem = 81920              # min 1024, size in KB
>
> # - Free Space Map -
>
> max_fsm_pages = 40000           # min max_fsm_relations*16, 6 bytes each
> max_fsm_relations = 2000        # min 100, ~50 bytes each
>
>
> Any suggestions the even reduce more the dump period?
>
> Thank you very much.
To reduce dump period I suggest you to use the unix pipes :

pgdumps $PSOPTIONS | psql $database

I make always like this as it 's a lot faster

Olivier



view thread (12+ messages)

Message-ID: <458AE6FD.2010004@cerene.fr>
Permalink:  ../458AE6FD.2010004@cerene.fr/
Also on:    postgresql.org/message-id/458AE6FD.2010004@cerene.fr

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: olivier.boissard@cerene.fr, arnaulist@andromeiberica.com
  Subject: Re: Suggestions needed about how to dump/restore a database
  In-Reply-To: <458AE6FD.2010004@cerene.fr>
  References: <45881D1A.6090904@andromeiberica.com> <458AB4AA.7000902@andromeiberica.com> <458AE6FD.2010004@cerene.fr>

* 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