|From:||Jan Urbański <wulczer(at)wulczer(dot)org>|
|To:||Steve Singer <ssinger_pg(at)sympatico(dot)ca>|
|Cc:||Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: pl/python SPI in subtransactions|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 29/01/11 22:13, Jan Urbański wrote:
> On 29/01/11 22:10, Steve Singer wrote:
>> On 11-01-29 03:39 PM, Jan Urbański wrote:
>>> D'oh, you're right, thanks. Attached patch with fix. Curiosly, right now
>>> in master your example with plpy.prepare will result in "savepoint"
>>> being swallowed, but it's of course better to react with an error.
>> This seems to fix it.
>> You mentioned that you were going to add a few paragraphs to the
>> documentation saying that you can now actually catch SPI errors. I
>> haven't seen that yet.
> Yeah, I'm procrastinating the doc writing part ;) Will spit something
> out by the end of the (CET) day.
Done, added a small example in the Database Access section.
|Next Message||Jan Urbański||2011-01-30 23:10:53||Re: pl/python SPI in subtransactions|
|Previous Message||Robert Haas||2011-01-30 22:55:51||Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)|