From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | simon(at)2ndquadrant(dot)com |
Cc: | josh(at)agliodbs(dot)com, 'Rob Fielding' <rob(at)dsvr(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: WAL Optimisation - configuration and usage |
Date: | 2004-03-03 00:01:11 |
Message-ID: | 40452047.6030501@samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-pitr pgsql-performance |
Simon Riggs wrote:
>>Josh Berkus wrote
>>
>>>Simon Riggs wrote
>>>Please set WAL_DEBUG to 1 so we can see a bit more info: thanks.
>>
>>I'm pretty sure that WAL_DEBUG requires a compile-time option.
>
> I'm surprised, but you are right, the manual does SAY this requires a
> compile time option; it is unfortunately not correct.
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.
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Hebbron | 2004-03-03 01:20:43 | Re: User defined types -- Social Security number... |
Previous Message | Curt Sampson | 2004-03-02 23:25:07 | Re: Check Constraints and pg_dump |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-03-03 18:58:20 | Re: WAL Optimisation - configuration and usage |
Previous Message | Simon Riggs | 2004-03-02 22:16:12 | Re: WAL Optimisation - configuration and usage |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff | 2004-03-03 02:07:10 | Re: Scaling further up |
Previous Message | johnnnnnn | 2004-03-02 23:25:41 | Re: Scaling further up |