Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpRiW-000598-Ai for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2013 23:23:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UpRiV-0002bK-Kg for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2013 23:23:07 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpRiU-0002bE-Su for pgsql-admin@postgresql.org; Wed, 19 Jun 2013 23:23:07 +0000 Received: from mail-pb0-x230.google.com ([2607:f8b0:400e:c01::230]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpRiS-0002gL-KS for pgsql-admin@postgresql.org; Wed, 19 Jun 2013 23:23:05 +0000 Received: by mail-pb0-f48.google.com with SMTP id ma3so5563731pbc.35 for ; Wed, 19 Jun 2013 16:23:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer:x-gm-message-state; bh=glcVBVAXhxuxt2nYdcYaD72NIq1Gt13FDhaYo4TZINw=; b=Ud5NNDUORa8JRMCqCHxnTIhbkgN4uQlnbRq4QdNXPQvaj9IDESWIWdNfw1A321O+El hZ6RoDxPtWmKbrAEfo/wE94obWRNUlq8U9cDVfe1Qy+c3BBoLwhpqheb3dSR5barEQUD k8SPwOSooE8wC3JRFF/Xp4RAorpNv/v7PtlA3eZnZQySprzkVjSde4eSdEYRNTz4nvSW 2m280c41N2Eg74HwHMxObOT71cP4E1qamc8YEpKZMQgaUA96i6qNL5z9djhPSFnfSUkr s7PQF4atSDzmJID3p/aejPIv0Y09fW3rTvKBzui4MBm12Dc3oaujx6WxAkCFePyTxw9y ku9g== X-Received: by 10.66.7.100 with SMTP id i4mr8593552paa.210.1371684182865; Wed, 19 Jun 2013 16:23:02 -0700 (PDT) Received: from [10.0.1.37] (rt.sdillion.customer.centurytel.net. [209.206.228.1]) by mx.google.com with ESMTPSA id qe10sm24978473pbb.2.2013.06.19.16.23.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 16:23:01 -0700 (PDT) From: Sean Dillon Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: excessive WAL activity Message-Id: <3F2CE3AE-231C-4B80-A48D-3ABC9C8CE6C7@dillonsoftware.com> Date: Wed, 19 Jun 2013 17:22:59 -0600 To: pgsql-admin@postgresql.org Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-Gm-Message-State: ALoCoQnq45L3HNW1+OztDsa8lQq7z6l9S4EwpQubrBajgQ0Ln9TzJ4ZyRohlfMeJzcICzjIx6jJR X-Pg-Spam-Score: 1.5 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Just turned on WAL archiving to an S3 bucket for a small database - total s= ize of perhaps 2-4G. After turning on achiving, we're seeing WAL logs writ= ten to S3 at the rate of about 1G every 3 minutes. That seems completely u= nreasonable given usage of the db. I can even see that nearly nothing is h= appening with this: select datname, usename, procpid, client_addr, waiting, query_start, curren= t_query from pg_stat_activity; Nearly every time I run that, all 20 connections have current_query =3D ''. Does current_query include inserts, updates, and deletes or just se= lect statements? Any ideas what to look for or how to solve this? --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin