Re: assert in nested SQL procedure call in current HEAD - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: assert in nested SQL procedure call in current HEAD
Date
Msg-id 87wov4rm72.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: assert in nested SQL procedure call in current HEAD  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: assert in nested SQL procedure call in current HEAD
Re: assert in nested SQL procedure call in current HEAD
List pgsql-hackers
>>>>> "Peter" == Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:

 >> Did you miss the fact that the issue only occurs when the top-level
 >> procedure does a rollback? The problem is not with nested calls, but
 >> rather with the fact that commit or rollback is leaving
 >> ActiveSnapshot unset, which is (as Tom pointed out at the linked
 >> post) not the expected condition inside PL code.

 Peter> We need that so that we can run things like SET TRANSACTION
 Peter> ISOLATION.

While testing this, I ran into another semi-related issue:
shmem_exit_inprogress isn't ever being cleared in the postmaster, which
means that if you ever have a crash-restart, any attempt to do a
rollback in a procedure will then crash or get some other form of
corruption again every time until you manually restart the cluster.

-- 
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: Tom Lane
Date:
Subject: Re: why partition pruning doesn't work?