Subject: Re: amount of WAL logs larger than expected
To: Mark Steben <mark.steben@drivedominion.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
References: 
 <CADyzmywE6B6SXnDxofNNVGagnH8wj0+44f09_QiJ7pzPDP0a=w@mail.gmail.com>
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
Message-ID: <5730D69F.3030208@commandprompt.com>
Date: Mon, 9 May 2016 11:27:43 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: 
 <CADyzmywE6B6SXnDxofNNVGagnH8wj0+44f09_QiJ7pzPDP0a=w@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 05/09/2016 11:23 AM, Mark Steben wrote:
> Good afternoon
>
> We run postgres 9.2.12  and run vacuum on a 540GB database.
>
> I've attached a 'show all' for your reference.  With CHECkPOINT_SEGMENTS
> set at 128
> and CHECKPOINT_COMPLETION_TARGET set at 0.9 I wouldn't expect the number
> of logs in pg_xlog to creep much over 400.  But when we run vacuum, the
> number can climb to over 5000 and threatens to blow out on space.  Is
> there something else I should be looking at causing this unexpected
> number of logs?
>
> Our server is also master for a slony1.2.2.3 slave and also to a hot
> standby server.

Are you archiving to your hot standby or streaming? If you are 
archiving, you may not be returning a proper success code and thus 
postgresql is keeping logs.

Also, you are well behind production (9.2.16) and there are 
*significant* bug fixes in the release gaps between.

JD

-- 
Command Prompt, Inc.                  http://the.postgres.company/
                         +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin