On Tue, Jul 7, 2015 at 03:21:50PM -0400, Bruce Momjian wrote:
> On Tue, Jul 7, 2015 at 01:05:09PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > On Tue, Jul 7, 2015 at 11:48:13AM -0400, Tom Lane wrote:
> > >> It's a bug. Back-patch as needed.
> >
> > > Doesn't that cause translation s
On Tue, Jul 7, 2015 at 01:05:09PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Tue, Jul 7, 2015 at 11:48:13AM -0400, Tom Lane wrote:
> >> It's a bug. Back-patch as needed.
>
> > Doesn't that cause translation string differences that are worse than
> > the original bug, e.g.:
> >
Bruce Momjian writes:
> On Tue, Jul 7, 2015 at 11:48:13AM -0400, Tom Lane wrote:
>> It's a bug. Back-patch as needed.
> Doesn't that cause translation string differences that are worse than
> the original bug, e.g.:
> psql_error("\\pset: allowed formats are unaligned, aligned, wrapped,
>
On Tue, Jul 7, 2015 at 11:48:13AM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I have discovered that psql \pset format does not display
> > "latex-longtable" as a valid value, e.g.:
>
> > test=> \pset format kjasdf
> > \pset: allowed formats are unaligned, aligned, wrapped, html,
Bruce Momjian writes:
> I have discovered that psql \pset format does not display
> "latex-longtable" as a valid value, e.g.:
> test=> \pset format kjasdf
> \pset: allowed formats are unaligned, aligned, wrapped, html, asciidoc,
> latex, troff-ms
> With the attached patch, the latex
