Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d0Ujh-0002ms-Gr for pgsql-admin@arkaria.postgresql.org; Tue, 18 Apr 2017 15:08:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d0Ujh-0000xR-3t for pgsql-admin@arkaria.postgresql.org; Tue, 18 Apr 2017 15:08:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d0UhP-0008J3-4C for pgsql-admin@postgresql.org; Tue, 18 Apr 2017 15:05:47 +0000 Received: from resqmta-ch2-04v.sys.comcast.net ([2001:558:fe21:29:69:252:207:36]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d0UhJ-0005JS-NE for pgsql-admin@postgresql.org; Tue, 18 Apr 2017 15:05:46 +0000 Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-04v.sys.comcast.net with SMTP id 0Uh5dipEzscBP0UhCdhfgN; Tue, 18 Apr 2017 15:05:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1492527934; bh=JfJspbGqs8ZLcTSCtsxsVzch8jhYnA//pBqMa9K1dXs=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=M7N+rJnppb4PLuoGdNPQxqq06N2o/sNtv/xPsMkhxKR48ptiQWlP+h+FHTZbKEZ4F KPokcRvKiG8vieyNfzA/QMoUMvovHOHnt+34bmJL4A3+rnRSohzGQ0Rv6nMbslrJyy oh9zgdU2XFWFhpzoe5Jp0cF4jQF1LvX4Q88qAOG1QFrpGuTnkH8sFodMtotz4BXXl3 phxr6BZ3VtYWqM7tTMiuLSzhjDRp4E+v4mPD605WQ7V+I/WikLmMcnv9MXBMnbpFsL UJlWbzz/AEL0EjTYUYu8sFaRTK4A/I7mBpNTzT+FhmVgGzMc9igxo8jcqjuhsAIZUi 1UR6hh9MR8l/w== Received: from jsievers.comcast.net ([12.187.116.132]) by resomta-ch2-14v.sys.comcast.net with SMTP id 0Uh1deeFdoAcF0Uh4dXaTX; Tue, 18 Apr 2017 15:05:32 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 4738626005E; Tue, 18 Apr 2017 10:05:23 -0500 (CDT) From: Jerry Sievers To: M Kiesewetter Cc: pgsql-admin@postgresql.org Subject: Re: Question about pg_xlog References: Date: Tue, 18 Apr 2017 10:05:23 -0500 In-Reply-To: (M. Kiesewetter's message of "Tue, 18 Apr 2017 16:36:07 +0200") Message-ID: <87tw5lpxho.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-CMAE-Envelope: MS4wfB0B5u3WBVToUITW63Nv2qHokkhT2UJcEmWI13+mGyk4JPKOVxEZNjGATnlAmfVaFeQbz61guuuSnNoX5WPPEn+GKgXR+r0LcidKwthzxasVn6C/+6mG LEhenYIxEBTZT2CUlzgxWg0Cz8dCaK0KMB64hu8uIXDsABRv4DP0dkhB2gsb4RRkHjbxcqp48KEeB99dWChAkx+3Voze+R+OwiH8S5Wh2W2Wr6vWzMwq2bK5 X-Pg-Spam-Score: -2.7 (--) 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 M Kiesewetter writes: > Hi everyone, > > I'm new to Postgresql and have a test environment with Postgresql > 9.4.5 running on Linux. > Today I noticed that the pg_xlog was filled up to 18 Gb. > I have:=C2=A0 > - wal_level=3Dhot_standby=C2=A0 > -=C2=A0wal_keep_segments =3D 100 > - hot_standby =3D on > archive_mode =3D on > > It's a test environment en I did a pg_resetxlogs() on the 6th of > April. > I know that I shouldn't use this, and that it's only a last resort. > When I look in de pg_xlog directory I see xlog files that are kept > sinds that time. > When i look at the archive_status directory I see that all of the > files have the suffix of .done. > All the other xlogs from the time before the resetlogs are cleaned up > as I expected. > But I don't understand why the other xlogs aren't recycled. I'd start by looking for dormant replication slots. select * from pg_replication_slots; HTH > I am looking for ways to find out why my pg_xlog is filling up. > - I checked the alertlog of the postgresql instance --> no errors > - I checked the WAL file location to see if the xlogs are being > archived --> they are present > > Are there more ways to find out why my pg_xlog is filling up? > Is the pg_resetxlogs the reason why the older xlogs are not recycled? > > I Hope that someone can help me. > Thanks in advance. > Regards, > Mariane > > > --=20 Jerry Sievers e: jerry.sievers@comcast.net p: 312.241.7800 --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin