| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Alex Piyevsky <Alex_Piyevsky(at)ibi(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2812: Transaction is aborted after error |
| Date: | 2006-12-06 22:42:47 |
| Message-ID: | 20061206224247.GJ30502@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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:
>
> current transaction is aborted, commands ignored until end of transaction
> block
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex_Piyevsky | 2006-12-06 22:46:06 | Re: BUG #2812: Transaction is aborted after error |
| Previous Message | Tom Lane | 2006-12-06 22:20:41 | Re: 8.2 bug with outer join reordering |