Re: Sloppy SSPI error reporting code

From: Noah Misch <noah(at)leadboat(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Sloppy SSPI error reporting code
Date: 2015-04-04 00:32:08
Message-ID: 20150404003208.GB1147382@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 02, 2015 at 07:31:52AM -0400, Bruce Momjian wrote:
> On Thu, Apr 2, 2015 at 01:44:59AM -0400, Noah Misch wrote:
> > On Wed, Apr 01, 2015 at 10:49:01PM -0400, Bruce Momjian wrote:
> > > On Sat, Jan 10, 2015 at 02:53:13PM -0500, Tom Lane wrote:
> > > > While looking at fe-auth.c I noticed quite a few places that weren't
> > > > bothering to make error messages localizable (ie, missing libpq_gettext
> > > > calls), and/or were failing to add a trailing newline as expected in
> > > > libpq error messages. Perhaps these are intentional but I doubt it.
> > > > Most of the instances seemed to be SSPI-related.
> > > >
> > > > I have no intention of fixing these myself, but whoever committed that
> > > > code should take a second look.
> > >
> > > I looked through that file and only found two cases; patch attached.
> >
> > Tom mentioned newline omissions, which you'll find in pg_SSPI_error().
>
> Oh, I accidentally saw the backend version of that function, which
> looked fine. I have attached a patch for that.

That patch looks reasonable.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Qingqing Zhou 2015-04-04 01:00:37 COALESCE() query yield different result with MJ vs. NLJ/HJ
Previous Message John Gorman 2015-04-03 21:51:52 Re: Compile warnings on OSX 10.10 clang 6.0