Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gOCv5-0008CZ-Q9 for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Nov 2018 02:34:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gOCsx-0003wh-9Q for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Nov 2018 02:32:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gOCsw-0003wa-O8 for pgsql-bugs@lists.postgresql.org; Sun, 18 Nov 2018 02:32:30 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gOCst-0001Tj-Up for pgsql-bugs@lists.postgresql.org; Sun, 18 Nov 2018 02:32:29 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 40F6D5F79C; Sat, 17 Nov 2018 21:32:27 -0500 (EST) Date: Sat, 17 Nov 2018 21:32:27 -0500 From: Stephen Frost To: Tom Lane Cc: ertugrul9090@gmail.com, Peter Eisentraut , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15511: Drop table error "invalid argument" Message-ID: <20181118023227.GM3415@tamriel.snowman.net> References: <15511-1d8b6a0bc874112f@postgresql.org> <2510.1542487896@sss.pgh.pa.us> <7717.1542493968@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Cqq5NadOW2RfLMJ/" Content-Disposition: inline In-Reply-To: <7717.1542493968@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Cqq5NadOW2RfLMJ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --Cqq5NadOW2RfLMJ/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJb8M86AAoJEO1sijiDR2RVg38P+gP0dkO2uONfzNQ3FawrmaAD kQyoJy4eUAvGP8+2czRqdD5MbISHEZQ40AyGqG/IGIvh/apMxoPgKuCdx7x26GZd 0bBvLXtdkU33+W0+oFDjB7JgsF6uVKYXWcNJfK0lg8saaz4+6Kwg/OIME3afs4hP tyMiawN7GN+JjZNnESW/vtkzFXoy0uvgrBTZUnwuZYtjX1qE5XtuFjzGiBJJzuoe JYtBHmLaw5tJ16LihBssuJnb/HO6e/IktzlDNxylOSRGGkQHY8HG3o3q4ZMiYqxZ hPFrviza9qKbuvPsthF9FSvbNcrnmRnvqrhvVBprtkeRpB5OA9qCkbfjXgcRYRI4 MjKCCGKLrs6C19wBWV7Ftq8SlIZNW2ijxxmfjUnLd8YOc6VrZPoMxqAty1B62QlB 8rV2cFk0lvAjLEqPoVfHhBawVRqSW0XrKvxEfoqXDDov7ApzuATvnBqznRI2EeI9 KIB9mvr6wyDas4KhGkOpgvDp60RiSJ6JToBh1mtOaBBSCqOl9xN5cwfSX4s3RV5k us7hXN/0xLyos9GdsQAssdyvrFnPRM8sam/nzj9rP4AbJbEMSpdvg1nSA4zQ4NaY BdFz8LqWCOGoNJLWDGQr95TrMPol8hS8Vj+zuLuy9Ik7kXT6mDinNTFajFggehTe iU2lSIqyhRGtnr5fQB6Z =+QMm -----END PGP SIGNATURE----- --Cqq5NadOW2RfLMJ/--