| From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Asif Naeem <asif(dot)naeem(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plpython issue with Win64 (PG 9.2) |
| Date: | 2012-07-05 19:51:42 |
| Message-ID: | 4FF5F04E.50805@wulczer.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2012-07-05 20:10:08 | obsolete copyright notice |
| Previous Message | Heikki Linnakangas | 2012-07-05 19:37:05 | Re: plpython issue with Win64 (PG 9.2) |