On Mon, Jun 4, 2012 at 8:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In addition, error message above seems corrupted in my environment.
>> Here we check not-escaped control character, so printing it with %c
>> formatting might break log files. How about using decimal or hex dump
>> in such cases?
> And so is that. IMO the error reporting in this module could stand to
> be reviewed altogether for compliance with our message guidelines.
> (For starters, why is it using errdetail_internal?) I refrained from
> editorializing on-the-fly, but I'm not too pleased with what I saw.
Huh. I have no idea why I thought errdetail_internal was a good idea.
Should we just change all those to errdetail?
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Robert Haas||Date: 2012-06-08 17:37:53|
|Subject: Re: error connecting to postgresql by pgadmin|
|Previous:||From: Simon Riggs||Date: 2012-06-08 16:39:27|
|Subject: Re: BUG #6661: out-of-order XID insertion in KnownAssignedXids|