Re: plpython issue with Win64 (PG 9.2) - Mailing list pgsql-hackers

From Jan Urbański
Subject Re: plpython issue with Win64 (PG 9.2)
Date
Msg-id 4FF5F04E.50805@wulczer.org
Whole thread Raw
In response to Re: plpython issue with Win64 (PG 9.2)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On 05/07/12 21:37, Heikki Linnakangas wrote:
> Committed. This bug was present in versions >= 9.0, so backpatched.

Thanks!

> I used ereport() rather than elog() in the error message. Correct me if
> that was wrong, but the point was to avoid PLy_elog(), because that
> might cause recursion, and ereport() should be ok. I believe the message
> should be translated, as it's quite possible to get that error, at least
> if you use SQL_ASCII, so ereport() is more approriate than elog().

Yes, you're absolutely right.

Cheers,
Jan


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: plpython issue with Win64 (PG 9.2)
Next
From: Antonin Houska
Date:
Subject: obsolete copyright notice