Subject: Re: number os commands inside transaction block
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Luiz Rafael Culik Guimaraes <culikr@brturbo.com>
Cc: Michael Fuhr <mike@fuhr.org>, pgsql-sql@postgresql.org
In-Reply-To: <045701c507e4$5c1c1790$0105a8c0@luiz>
References: <6c21003b0501301141234c256b@mail.gmail.com>
	<20050131132701.G12960@megazone.bigpanda.com>
	<043f01c507df$9174a790$0105a8c0@luiz>
	<20050131221306.GA51538@winnie.fuhr.org>
	<045701c507e4$5c1c1790$0105a8c0@luiz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1107211755.16640.157.camel@state.g2switchworks.com>
Mime-Version: 1.0
Date: Mon, 31 Jan 2005 16:49:15 -0600

On Mon, 2005-01-31 at 16:29, Luiz Rafael Culik Guimaraes wrote:
> Hi Michael Fuhr
> >> how i can increse the number of commands in an transaction block
> >
> > What do you mean?  What problem are you trying to solve?
>=20
> i=C2=B4m trying to solve the follow message
> current transaction is aborted, queries ignored until end of transaction
> block
>=20
> some one tell me this is defined inside postgres sources
> i recive this message when i execute an certain number of queries inside =
an=20
> begin/commit block

This is normal postgresql behaviour, and can't really be changed.=20
However, with the advent of savepoints in 8.0, it is now possible to
detect such errors and roll back so you can then continue.  Without
using savepoints with rollback to the given save point, however, there's
not much way to get around it.

It sounds to me like you're getting an error somewhere in your scripts
you need to look into.