Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
От | Florian Pflug |
---|---|
Тема | Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT |
Дата | |
Msg-id | 36BF6DA2-AADF-46BC-81E0-5D03D620FFA0@phlo.org обсуждение исходный текст |
Ответ на | Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT
Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT |
Список | 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
Вложения
В списке pgsql-hackers по дате отправления: