Date: Mon, 31 Jan 2005 15:54:05 -0700
From: Michael Fuhr <mike@fuhr.org>
To: Luiz Rafael Culik Guimaraes <culikr@brturbo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: number os commands inside transaction block
Message-ID: <20050131225405.GA51669@winnie.fuhr.org>
References: <6c21003b0501301141234c256b@mail.gmail.com>
	<20050131132701.G12960@megazone.bigpanda.com>
	<043f01c507df$9174a790$0105a8c0@luiz>
	<20050131221306.GA51538@winnie.fuhr.org>
	<045701c507e4$5c1c1790$0105a8c0@luiz>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <045701c507e4$5c1c1790$0105a8c0@luiz>

On Mon, Jan 31, 2005 at 08:29:42PM -0200, Luiz Rafael Culik Guimaraes wrote:
> 
> i´m trying to solve the follow message
> current transaction is aborted, queries ignored until end of transaction
> block

A previous command in the transaction has failed; no more commands
will be executed until you issue a ROLLBACK (or a COMMIT, but the
transaction will be rolled back due to the error).  If you're doing
error checking on every command then you should be able to discover
which command failed.

PostgreSQL 8.0 has savepoints so you can roll back part of a
transaction and continue after an error, but that might not be
what you need.

> some one tell me this is defined inside postgres sources
> i recive this message when i execute an certain number of queries inside an 
> begin/commit block

Transactions can have 2^32 - 1 (4294967295) commands, so I'd be
surprised if you were hitting that limit.  If you were, you should
see the following error:

cannot have more than 2^32-1 commands in a transaction

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/