Re: PL/Python SQL error code pass-through
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Jan Urbański <wulczer@wulczer.org>
Cc: Mika Eloranta <mel@ohmu.fi>, pgsql-hackers@postgresql.org
Date: 2011-11-24T15:15:49Z
Lists: pgsql-hackers
On 24.11.2011 10:07, Jan Urbański wrote: > On 23/11/11 17:24, Mika Eloranta wrote: >> Hi all, >> >> [PL/Python in 9.1 does not preserve SQLSTATE of errors] > > Oops, you're right, it's a regression from 9.0 behaviour. > > The fix looks good to me, I changed one place to indent with tabs > instead of spaces and added a regression test. Thank you, both. Is there some other fields that we should propagate from the original error message that we're missing? Like, context and file/line information? Or are those left out on purpose? I wonder if we should have a more wholesale approach, and store the whole ErrorData struct somewhere, and only add some extra context information with errcontext(). > I think this should be backpatched to 9.1, no? Yeah, it should. Your patch probably makes most sense for backpatching, even if we do something more radical on master. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com