Re: WAL Optimisation - configuration and usage

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL Optimisation - configuration and usage
Date: 2004-03-03 18:58:20
Message-ID: 200403031058.20934.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-hackers-pitr pgsql-performance

Neil,

> Actually, the manual is correct: in 7.4 and earlier releases, enabling
> wal_debug can be done without also setting a compile-time #ifdef. As
> of current CVS HEAD, the WAL_DEBUG #ifdef must be defined before this
> variable is available.

Hmmm. I was told that it was this way for 7.4 as well; that's why it's in
the docs that way.

--
-Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2004-03-03 20:28:15 Re: [pgsql-hackers-win32] What's left?
Previous Message Bruce Momjian 2004-03-03 17:52:40 Re: Tablespaces

Browse pgsql-hackers-pitr by date

  From Date Subject
Next Message Simon Riggs 2004-03-03 21:40:09 The Return of PITR
Previous Message Neil Conway 2004-03-03 00:01:11 Re: WAL Optimisation - configuration and usage

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2004-03-03 18:59:19 Re: Database Server Tuning
Previous Message scott.marlowe 2004-03-03 18:23:11 Re: Scaling further up