pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Ziegelwanger, Silvio <Silvio.Ziegelwanger@fabasoft.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Monitoring Transaction Log size
Date: Wed, 17 Jan 2007 17:38:37 -0500
Message-ID: <6235.1169073517@sss.pgh.pa.us> (raw)
In-Reply-To: <45AE6376.7060606@commandprompt.com>
References: <B710F3299F04664DB6B37C258FDEEB9402A617@FABAMAIL.fabagl.fabasoft.com>
	<45AE6376.7060606@commandprompt.com>

"Joshua D. Drake" <jd@commandprompt.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



view thread (7+ messages)  latest in thread

Message-ID: <6235.1169073517@sss.pgh.pa.us>
Permalink:  ../6235.1169073517@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6235.1169073517@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jd@commandprompt.com, Silvio.Ziegelwanger@fabasoft.com
  Subject: Re: Monitoring Transaction Log size
  In-Reply-To: <6235.1169073517@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox