DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=JQJ07mlDzypXd3TXP6k/bPSPRukcJ/sR2At0zTt3zxrlBOGkZ6jq+BMQbfX43zqh4AXk7wR8a5jrWy7RjP1xKwYX60H4lHWI1cboBwJztes07VVIpf6nayYRpfmHWGOKK5+hKR7nITd1gJ62RiFy5PzAJbucVLhq5rTYhh0wEe4=;
Date: Mon, 24 Sep 2007 07:03:47 -0700 (PDT)
From: Michael Cochez <michaelcochez@yahoo.com>
Subject: error in documentation?
To: pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1779450781-1190642627=:93299"
Content-Transfer-Encoding: 8bit
Message-ID: <71337.93299.qm@web33515.mail.mud.yahoo.com>

--0-1779450781-1190642627=:93299
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

In http://www.postgresql.org/docs/8.2/static/tutorial-transactions.html
"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it."
mustn't it be : 
"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. Keep in mind that rolling back to a savepoint will automatically release all savepoints that were defined after it and releasing a savepoint will automatically release all savepoints defined before it."

if not, could you please explain why this decision is made?
thanks,
Michael
       
---------------------------------
Don't let your dream ride pass you by.    Make it a reality with Yahoo! Autos. 
--0-1779450781-1190642627=:93299
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<!-- type = text -->In http://www.postgresql.org/docs/8.2/static/tutorial-transactions.html<br>"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it."<br>mustn't it be : <br>"After rolling back to a savepoint, it continues to be defined, so you can roll back to it several times. Conversely, if you are sure you won't need to roll back to a particular savepoint again, it can be released, so the system can free some resources. <span style="color: rgb(255, 0, 0);">Keep in mind that rolling back to a savepoint will automatically release all savepoints that were defined after it and releasing a savepoint will automatically release all savepoints
 defined before it.</span>"<br><br>if not, could you please explain why this decision is made?<br>thanks,<br>Michael<p>&#32;
      <hr size=1>Don't let your dream ride pass you by.  <a href="http://us.rd.yahoo.com/evt=51200/*http://autos.yahoo.com/index.html;_ylc=X3oDMTFibjNlcHF0BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDYXV0b3MtZHJlYW1jYXI-">  Make it a reality</a> with Yahoo! Autos.


--0-1779450781-1190642627=:93299--