| From: | dhanuj hippie <dhanuj(dot)hippie(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog keeps growing |
| Date: | 2017-02-28 05:49:54 |
| Message-ID: | CAGqAkKfckS7zYwcnf+nQvUpJeii5qkYP0pOR2c=5fMKR7n2c4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Based on my config, what is the max size this directory is expected to grow
? And how can I check whether this recycle/removal is happening fine ?
On Tue, Feb 28, 2017 at 10:08 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com
> wrote:
> On Tue, Feb 28, 2017 at 1:20 PM, dhanuj hippie <dhanuj(dot)hippie(at)gmail(dot)com>
> wrote:
> > So does it work like - it can go upto 16MB*1024 times which is 16GB, and
> > then this will be cleaned up automatically ?
>
> On a standby each time a restart point is created the oldest segments
> are either recycled or removed, wal_keep_segments retains more of
> that. You can look at KeepLogSeg() in
> src/backend/access/transam/xlog.c if you want..
> --
> Michael
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-02-28 06:17:15 | Re: pg_xlog keeps growing |
| Previous Message | Adrian Klaver | 2017-02-28 05:14:33 | Re: Shared WAL archive between master and standby: WALs not always identical |