From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Eduardo Morras <emorrasg(at)yahoo(dot)es>, "Powrie, William" <wpowrie(at)indracompany(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Ever increasing pg_clog disk usage v8.4 |
Date: | 2014-12-01 14:47:00 |
Message-ID: | 7814.1417445220@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Eduardo Morras <emorrasg(at)yahoo(dot)es> writes:
> "Powrie, William" <wpowrie(at)indracompany(dot)com> wrote:
>> The files in pg_clog increase on a day to day basis until the ramdisk
>> reaches 100% utilization. This takes roughly 30 days to occur and
>> postgresql fails at this point.
> pg_clog stores information about current commit status for open/active transactions. Do you close all transactions after they're work is done? Do you have any in "IDLE in transaction" state?
Leaving prepared transactions sitting (without committing them or
rolling them back) could do this as well, I believe.
8.4 seems to default to max_prepared_transactions = 0 so it would
take some extra work to shoot yourself in the foot that way, but
it's definitely possible.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-12-01 14:50:42 | Re: Ever increasing pg_clog disk usage v8.4 |
Previous Message | Reid Thompson | 2014-12-01 14:42:47 | Re: Re: Remote PostgreSQL database - C/C++ program / Unix / Required Libraries |