From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199806160243.WAA21381@candle.pha.pa.us>
Subject: Re: [QUESTIONS] errors on transactions and locks ?
To: sferac@proxy.bazzanese.com (Jose' Soares Da Silva)
Date: Mon, 15 Jun 1998 22:43:56 -0400 (EDT)
Cc: herouth@oumail.openu.ac.il,
 hackers@postgreSQL.org (PostgreSQL-development)
In-Reply-To: <Pine.LNX.3.96.980422113809.1139A-100000@proxy.bazzanese.com>
	from "Jose' Soares Da Silva" at Apr 22, 98 11:39:51 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> 
> On Tue, 21 Apr 1998, Herouth Maoz wrote:
> 
> Your example is very exhaustive Herouth. I tried it with SOLID and in fact
> it leaves SOLID database inconsistent.
> 
> I see that PostgreSQL BEGIN/END statements are slight different from SQL
> transactions that begins with a implicit begin transaction (no BEGIN command)
> and ends with a ROLLBACK or COMMIT statement.
> 
> Until now I thought that END was equal to COMMIT but in the case of:
>        NOTICE:  (transaction aborted): queries ignored until END
>        *ABORT STATE*
> in this case END stands for ROLLBACK/ABORT I think it isn't enough clear.
> (I thought all reference to END were changed to COMMIT).
> PostgreSQL don't say to the user that all his work will be lost even if he do
> COMMIT.
> 
> Maybe the following warn is more clear:
>        NOTICE:  (transaction aborted): queries ignored until COMMIT/ROLLBAK
>        WARN:  all changes will be lost even if you use COMMIT.

I have changed the text to read:

             "all queries ignored until end of transaction block"); 
 

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)