Re: proposal: PL/Pythonu - function ereport - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: PL/Pythonu - function ereport
Date
Msg-id CAFj8pRDk9z4F7D6fG9TtpG3LVfq0CVosPHroC2g_uLrF==a_vQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: PL/Pythonu - function ereport  (Catalin Iacob <iacobcatalin@gmail.com>)
Responses Re: proposal: PL/Pythonu - function ereport  (Robert Haas <robertmhaas@gmail.com>)
Re: proposal: PL/Pythonu - function ereport  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Hi

2016-03-01 18:48 GMT+01:00 Catalin Iacob <iacobcatalin@gmail.com>:
On 3/1/16, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> I though about it before and I prefer variant with possibility to enter
>> message as keyword parameter.

That's also ok, but indeed with a check that it's not specified twice
which I see you already added.

> I merged your patches without @3 (many thanks for it). Instead @3 I
> disallow double message specification (+regress test)

Great, welcome. Ran the tests for plpython-enhanced-error-06 again on
2.4 - 2.7 and 3.5 versions and they passed.

I see the pfree you added isn't allowed on a NULL pointer but as far
as I see message is guaranteed not to be NULL as dgettext never
returns NULL.

I'll mark this Ready for Committer.

Thank you very much

Nice day

Pavel

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Relation extension scalability
Next
From: Tom Lane
Date:
Subject: Re: TAP / recovery-test fs-level backups, psql enhancements etc