Re: BUG #2812: Transaction is aborted after error - Mailing list pgsql-bugs

From
Subject Re: BUG #2812: Transaction is aborted after error
Date
Msg-id 8EC4F0A8AC7A6D40BF9C55E32249A9165BF69E@IBIUSMBSA.ibi.com
Whole thread Raw
In response to BUG #2812: Transaction is aborted after error  ("Alex Piyevsky" <Alex_Piyevsky@ibi.com>)
List pgsql-bugs
Thank you for your help and prompt response.

Regards,
Alex

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@commandprompt.com]=20
Sent: Wednesday, December 06, 2006 5:43 PM
To: Piyevsky, Alex
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #2812: Transaction is aborted after error

Alex Piyevsky wrote:

> We issue a command which drops the existing table and recreates the
table
> under the same name, all in one transaction.  If the table does not
> previously exist, an error message is returned for the drop command
and the
> transaction aborts with the following:
>=20
> current transaction is aborted, commands ignored until end of
transaction
> block=20

This is the intended behavior.  In 8.2 you can use "DROP TABLE IF
EXISTS".  In previous versions you can set a savepoint before the DROP
TABLE; or you can do the DROP TABLE outside the transaction.

--=20
Alvaro Herrera
http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-bugs by date:

Previous
From: Michael Andreen
Date:
Subject: 8.2 bug: Mixing spi_prepare and spi_exec_query causes postgresql to terminate itself on bad argument types
Next
From: Ross Cohen
Date:
Subject: Re: BUG #2811: Error determining param type in prepared statement of unused variable