Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 2DEED2E006E for ; Mon, 5 May 2008 14:06:28 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 59933-05-4 for ; Mon, 5 May 2008 14:06:18 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by developer.postgresql.org (Postfix) with ESMTP id 3D0CB2E002D for ; Mon, 5 May 2008 14:05:05 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 76so1337005wra.10 for ; Mon, 05 May 2008 10:05:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=v2+xXnZO2ni6faqYo1v3jrLAs2mTCffEcuhQfAgT3cs=; b=AjTB6W/aZioizFuvvbJAptoil92eTGyAnc59DMITGF8pZWDIJ0YznMDFojUBKaUcsx6tS+P1vrhG8r8ePvCc3hboDibc0yAEhcBS3AaTaNPD9lFFaCs0UGk5srt4W1prBZwUuOqF80c2FLNJbLmcB75fzOn3FAREXlBbzQa+dbA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fQ0bBbsLENL31CqwospxseIfKR6fWBVf0f29c6XN9tV5jSqunwE++Dr6xMq4nK9NtJUS44Yp2GJuFe9n6XhNwP+y2dRuMqHM9lWNb/wkMxyP++Ngs3heXiKg/pyjEH3lAqhQJGMunL+0gVOtJeqTn1PoeMNX+NMXDJbIIE45Rtc= Received: by 10.115.73.20 with SMTP id a20mr5926936wal.142.1210007103798; Mon, 05 May 2008 10:05:03 -0700 (PDT) Received: by 10.114.137.7 with HTTP; Mon, 5 May 2008 10:05:03 -0700 (PDT) Message-ID: Date: Mon, 5 May 2008 11:05:03 -0600 From: "Scott Marlowe" To: "Campbell, Lance" Subject: Re: Backup causing poor performance - suggestions Cc: pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/56 X-Sequence-Number: 30024 On Mon, May 5, 2008 at 10:11 AM, Campbell, Lance wrote: > Scott, > The last 6 entries are when the system is not backing up. The system > was running fine. But the other entries are when it was backing up. > Reads seem to be fine but any operations that need to write data just > hang. Could you repost that as an attachment? the wrapping applied by your email client makes it very hard to read. Just perusing it, it doesn't look like you're CPU bound, but I/O bound. As Craig mentioned, you may do better with some form of replication solution here than pg_dumps. Given that your db can fit in memory (when you say it's 8G do you mean ON DISK, or in a backup? Big diff) then the only thing the backups should be slowing down are update queries. Select queries shouldn't even notice. However, there's a LOT of wait state, and only blocks out, not really many in, so I'm guessing that you've got a fair bit of writing going on at the same time as your backups.