Re: BUG #15511: Drop table error "invalid argument" - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #15511: Drop table error "invalid argument"
Date
Msg-id 131ffaa0-0dbd-6da2-cdad-7757e234d0cb@2ndquadrant.com
Whole thread Raw
In response to Re: BUG #15511: Drop table error "invalid argument"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 07/12/2018 00:38, Tom Lane wrote:
> ... so my preliminary result is that there's a *boatload* of "invalid"
> format strings in our translation files, all of them apparently with
> the extra-space disease.  See attached.

A bit of follow-up:  I have committed fixes for all the erroneous uses
of space "flags" in translated format strings.  These will then be in
the next minor releases.

I also looked into the gettext/msgfmt source code.  We know that it does
check for format string compatibility, but I found that it only checks
the general type, not the formatting flags.  I suppose this is not
unreasonable, since a translation might want to space or align something
differently.  So we still don't have an easy way to check for this in
the future.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: "Saul, Jean Paolo"
Date:
Subject: Re: BUG #15609: synchronous_commit=off insert performance regressionwith secondary indexes
Next
From: Peter Eisentraut
Date:
Subject: Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure