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

From Florian Pflug
Subject Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
Date
Msg-id 36BF6DA2-AADF-46BC-81E0-5D03D620FFA0@phlo.org
Whole thread Raw
In response to Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
List pgsql-hackers
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.

Unfortunately, this patch is untested. I couldn't get openjade + DocBook to work on OSX for some reason :-(

best regards,
Florian Pflug

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Tom Lane
Date:
Subject: Re: Regression testing for psql