On Wed, Feb 15, 2017 at 8:28 PM, Heikki Linnakangas <hlinn...@iki.fi> wrote: > Ah, found it. It was because of this change: > > Having two error codes with the same SQLSTATE is not cool, and tripped the > assertion in PL/python. I removed the new error code, it was only used in > one place, and ERRCODE_PROTOCOL_VIOLATIOn was more appropriate there anyway.
It seems that this one is on me. Thanks for looking at it. -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers