| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)mail(dot)com>, AI Rumman <rummandba(at)gmail(dot)com>, Pgsql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog is getting bigger |
| Date: | 2012-12-20 01:06:37 |
| Message-ID: | 26655.1355965597@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> On 12/19/2012 01:16 PM, Kevin Grittner wrote:
>> AI Rumman wrote:
>>> checkpoint_segments | 300
> Aah, just noticed the above.
I saw that too, but it doesn't seem to explain 20GB worth of pg_xlog.
The fine manual mentions somewhere that we can keep up to twice the
specified number of xlog segments, so one would expect at most 16MB
* 600 or about 9.6GB in pg_xlog. (And this is assuming that
checkpoint_timeout is large enough to let checkpoint_segments be the
controlling factor.) So there's something else going on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert James | 2012-12-20 01:28:22 | DONT_CARE Aggregate |
| Previous Message | Tom Lane | 2012-12-20 00:55:18 | Re: pg_xlog is getting bigger |