| 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: | 6235.1169073517@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2007-01-17 23:08:44 | Re: Configuration Advice |
| Previous Message | Kevin Hunter | 2007-01-17 22:15:24 | DB benchmark and pg config file help |