| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WAL_DEBUG logs spurious data |
| Date: | 2012-10-11 23:16:20 |
| Message-ID: | 50775344.2000906@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/11/2012 04:06 PM, Tom Lane wrote:
> Yeah, if we decide to stick with the limitation, some documentation
> would be called for. I remember having run into this and having removed
> functionality from an rm_desc function rather than question the premise.
> But maybe the extra functionality is worth the cycles.
Well, I've been interested in getting it correct, and didn't care about
performance.
But I can certainly imagine someone enabling it on a production system
to get more debug info. In which case performance would matter more.
However, WAL_DEBUG being a #define, I bet only very few admins do that.
So I tend towards sacrificing performance for better debug info in the
WAL_DEBUG case. (Especially given that you can still disable it via GUC).
Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-10-11 23:33:14 | Re: Deprecating RULES |
| Previous Message | Tom Lane | 2012-10-11 23:06:15 | Re: WAL_DEBUG logs spurious data |