Re: [HACKERS] Transaction control in procedures - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [HACKERS] Transaction control in procedures
Date
Msg-id 9b2a65db-dedf-bbeb-babf-9f926e947368@2ndQuadrant.com
Whole thread Raw
In response to Re: [HACKERS] Transaction control in procedures  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Transaction control in procedures
Re: [HACKERS] Transaction control in procedures
List pgsql-hackers

On 01/16/2018 10:16 AM, Peter Eisentraut wrote:
> On 1/15/18 12:57, Andrew Dunstan wrote:
>> This confused me slightly:
>>
>>     +    Transactions cannot be ended inside loops through query results
>>     or inside
>>     +    blocks with exception handlers.
>>
>> I suggest: "A transaction cannot be ended inside a loop over query
>> results, nor inside a block with exception handlers."
> fixed
>
>> The patch has bitrotted slightly in src/backend/commands/portalcmds.c
> merged
>
>> The plperl expected file needs updating. Also, why does spi_commit() in
>> a loop result in an error message but not spi_rollback()?
> This is all changed now after the patch for portal pinning in PL/Perl
> and PL/Python has been committed.  The attached patch behaves better.
>


Looks good. Marking ready for committer.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: let's not complain about harmless patch-apply failures
Next
From: Robert Haas
Date:
Subject: Re: TOAST table created for partitioned tables