| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Why does WAL_DEBUG macro need to be defined by default? |
| Date: | 2011-10-07 09:19:37 |
| Message-ID: | CAHGQGwGaXBydgtW4+NB5=3ZEE-3n7b3RNtm92HUpeHgf8Qt47w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 truncated whenever the database
system enters recovery. Indexes on unlogged tables are also unlogged.
Unlogged GiST indexes are not currently supported.
----------------------
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2011-10-07 10:21:27 | Re: [REVIEW] Patch for cursor calling with named parameters |
| Previous Message | Etsuro Fujita | 2011-10-07 09:09:44 | Re: WIP: Collecting statistics on CSV file data |