Re: Interpretting WAL debug.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Murthy Kambhampaty <Murthy(dot)Kambhampaty(at)goeci(dot)com>
Cc: "'Marc Mitchell'" <marcm(at)eisolution(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Interpretting WAL debug.
Date: 2002-08-29 17:39:51
Message-ID: 19818.1030642791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Murthy Kambhampaty <Murthy(dot)Kambhampaty(at)goeci(dot)com> writes:
> At bottom, I suspect you can get your machine tuned without WAL debug, and
> Bruce's paper on tuning, which it looks like you've been reading. I don't
> think, you need to turn on WAL debug for the particular question you asked.

I agree. The WAL debug code is really intended for *debugging* WAL, not
for tuning purposes. I think all you really need care about is whether
you get "new log file created" messages and what the frequency of
checkpoints is.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2002-08-29 17:44:20 Re: timeout
Previous Message Tom Lane 2002-08-29 17:37:31 Re: delete with referential integrity