Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
Date
Msg-id 4BFE109F.6050104@enterprisedb.com
Whole thread Raw
In response to Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
On 27/05/10 03:25, Florian Pflug wrote:
> On May 27, 2010, at 0:58 , Heikki Linnakangas wrote:
>> On 26/05/10 02:00, Sam Vilain wrote:
>>> Florian Pflug wrote:
>>>> On May 25, 2010, at 12:18 , Heikki Linnakangas wrote:
>>>>> Releasing the newer savepoint will cause the older one to again become accessible, as the doc says, but rolling
backto a savepoint does not implicitly release it. You'll have to use RELEASE SAVEPOINT for that.
 
>>>>
>>>> Ah, now I get it. Thanks.
>>>>
>>>> Would changing "Releasing the newer savepoint will cause ... " to "Explicitly releasing the newer savepoint" or
maybeeven "Explicitly releasing the newer savepoint with RELEASE SAVEPOINT will cause ..." make things clearer?
 
>>>
>>> Yes, probably - your misreading matches my misreading of it :-)
>>
>> +1.
>
> Patch that changes the wording to "Explicitly releasing the newer savepoint with RELEASE SAVEPOINT will cause ..." is
attached.

Thanks, committed. I left out the "Explicitly", though, because as Sam 
pointed out the newer savepoint can also be implicitly released by 
rolling back to an earlier savepoint.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Synchronization levels in SR
Next
From: Pavel Stehule
Date:
Subject: Re: functional call named notation clashes with SQL feature