pgsql: Fix gettext triggers specification

Started by Peter Eisentrautalmost 7 years ago3 messagescomitters
Jump to latest
#1Peter Eisentraut
peter_e@gmx.net

Fix gettext triggers specification

In cc8d41511721d25d557fc02a46c053c0a602fed0, the arguments of
warn_or_exit_horribly() were changed but this was not updated.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f2690338814738967d75cc1e35cc1cfac1a40710

Modified Files
--------------
src/bin/pg_dump/nls.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: pgsql: Fix gettext triggers specification

Peter Eisentraut <peter@eisentraut.org> writes:

Fix gettext triggers specification
In cc8d41511721d25d557fc02a46c053c0a602fed0, the arguments of
warn_or_exit_horribly() were changed but this was not updated.

Hm, so surely that should be back-patched into v12?

regards, tom lane

#3Peter Eisentraut
peter_e@gmx.net
In reply to: Tom Lane (#2)
Re: pgsql: Fix gettext triggers specification

On 2019-08-26 19:32, Tom Lane wrote:

Peter Eisentraut <peter@eisentraut.org> writes:

Fix gettext triggers specification
In cc8d41511721d25d557fc02a46c053c0a602fed0, the arguments of
warn_or_exit_horribly() were changed but this was not updated.

Hm, so surely that should be back-patched into v12?

Yup, I somehow missed pushing that branch.

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