Postgres Pro
Downloads
Home   >   mailing lists

Why does WAL_DEBUG macro need to be defined by default? - Mailing list pgsql-hackers

From Fujii Masao
Subject Why does WAL_DEBUG macro need to be defined by default?
Date
Msg-id CAHGQGwGaXBydgtW4+NB5=3ZEE-3n7b3RNtm92HUpeHgf8Qt47w@mail.gmail.com
Whole thread Raw
Responses Re: Why does WAL_DEBUG macro need to be defined by default?
Re: Why does WAL_DEBUG macro need to be defined by default?
List pgsql-hackers
Tree view 
Hi,

I found that by default WAL_DEBUG macro has been defined in
9.2dev and 9.1. I'm very surprised at this. Why does WAL_DEBUG
need to be defined by default? The performance overhead
introduced by WAL_DEBUG is really vanishingly low?

WAL_DEBUG was defined in the following commit:
53dbc27c62d8e1b6c5253feba04a5094cb8fe046

----------------------   Support unlogged tables.
   The contents of an unlogged table are WAL-logged; thus, they are not   available on standby servers and are
truncatedwhenever the database   system enters recovery.  Indexes on unlogged tables are also unlogged.   Unlogged GiST
indexesare not currently supported.
 
----------------------

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: WIP: Collecting statistics on CSV file data
Next
From: Yeb Havinga
Date:
Subject: Re: [REVIEW] Patch for cursor calling with named parameters