Re: WAL_DEBUG logs spurious data
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Markus Wanner <markus@bluegap.ch>, PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>
Date: 2013-01-25T21:27:18Z
Lists: pgsql-hackers
On Thu, Oct 11, 2012 at 07:06:15PM -0400, Tom Lane wrote: > Markus Wanner <markus@bluegap.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. I assume there is no TODO item or patch here. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +