Search Postgresql Archives
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: pgsql-general@xxxxxxxxxxxxxx
- Subject: Re: Backups
- From: Richard Harley <richard@xxxxxxxxxxxxxxx>
- Date: Thu, 15 Mar 2012 12:37:02 +0000
- In-reply-to: <CAKwGa_9v171YzWzJtOV4xNn==aXQLFt2fjaup5CV2vP2Fkmdag@mail.gmail.com>
- Organization: ScholarPack
- Reply-to: richard@xxxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20110922 Thunderbird/3.1.15
Thanks for a quick reply. The server has 6 cores, 6GB ram and top
gets to 2.3-2.5 load average when running the dumpall. So I assume
we are nowhere near this causing performance issues for users?|
On 15/03/12 12:21, Bèrto ëd Sèra wrote:
it's no easy answer. If your server has plenty of free
resources there won't be trouble, but I do have customers who
cannot even imagine of launching a dump in normal traffic hours.
How loaded is your box, currently?
On 15 March 2012 12:15, Richard Harley <richard@xxxxxxxxxxxxxxx>
Very simple question - does pg_dump/dumpall hit the server
in terms of database performance? We currently do nightly
backups and I want to move to hourly backups but not at the
expense of hogging all the resources for 5 mins.
Pg_dumpall is currently producing a 1GB file - that's the
combined size of around 30 databases and it takes around 5
mins to run.
If Pac-Man had affected us as kids, we'd all be running
around in a darkened room munching pills and listening to
[PHP on Windows]
[Find Someone Nice]
[Postgresql & PHP]