From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: ertugrul9090@gmail.com, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15511: Drop table error "invalid argument"
Date: Sat, 17 Nov 2018 21:32:27 -0500
Message-ID: <20181118023227.GM3415@tamriel.snowman.net> (raw)
In-Reply-To: <7717.1542493968@sss.pgh.pa.us>
References: <15511-1d8b6a0bc874112f@postgresql.org>
<2510.1542487896@sss.pgh.pa.us>
<7717.1542493968@sss.pgh.pa.us>
Greetings,
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> (4) However, that leaves us with a translation problem, because msgfmt
> doesn't detect some things that we'll fail on at runtime. What shall
> we do about that?
I realize this is pretty pie-in-the-sky, but maybe we should have a
buildfarm member that's actually running the regression suite with every
translation we support..? Of course, then we should also have our
regression tests actually causing every error message to be hit at least
once or we'd still possibly miss things.
A shorter path, though one with less additional benefits, would
presumably be to find a way to make msgfmt fail on things that we'll
fail on..? Or otherwise detect such cases..?
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: sfrost@snowman.net, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15511: Drop table error "invalid argument"
In-Reply-To: <20181118023227.GM3415@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox