Skip site navigation (1) Skip section navigation (2)

Re: Monitoring Transaction Log size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Ziegelwanger, Silvio" <Silvio(dot)Ziegelwanger(at)fabasoft(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Monitoring Transaction Log size
Date: 2007-01-17 22:38:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Ziegelwanger, Silvio wrote:
>> how can I monitor the size of the transaction log files using SQL Statements?

> You can't. You would have to write a custom function to heck the size of
> the xlog directory.

Perhaps more to the point, why do you think you need to?  pg_xlog should
stay pretty level at approximately 2*checkpoint_segments xlog files
(once it's ramped up to that size, which might take a heavy burst of
activity if checkpoint_segments is large).

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Chris BrowneDate: 2007-01-17 23:08:44
Subject: Re: Configuration Advice
Previous:From: Kevin HunterDate: 2007-01-17 22:15:24
Subject: DB benchmark and pg config file help

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group