Re: WAL_DEBUG logs spurious data

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Wanner <markus(at)bluegap(dot)ch>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL_DEBUG logs spurious data
Date: 2012-10-11 23:06:15
Message-ID: 2452.1349996775@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Markus Wanner <markus(at)bluegap(dot)ch> writes:
> On 10/11/2012 03:11 PM, Tom Lane wrote:
>> The original design intention was that rm_desc should not attempt to
>> print any such data, but obviously some folks didn't get the word.

> FWIW: in case the source code contains comments explaining that
> intention, I certainly missed them so far.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Wanner 2012-10-11 23:16:20 Re: WAL_DEBUG logs spurious data
Previous Message Josh Berkus 2012-10-11 22:59:55 Re: Deprecating RULES