Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings
Date: 2012-01-25 21:25:46
Message-ID: 1327526655-sup-2230@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Noah Misch's message of sáb ene 14 12:40:02 -0300 2012:
> It has bothered me that psql's \copy ignores the ON_ERROR_ROLLBACK setting.
> Only SendQuery() takes note of ON_ERROR_ROLLBACK, and \copy, like all
> backslash commands, does not route through SendQuery(). Looking into this
> turned up several other weaknesses in psql's handling of COPY.

Interesting.

Committed, thanks.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-25 21:57:08 Re: WIP patch for parameterized inner paths
Previous Message Giuseppe Sucameli 2012-01-25 21:19:46 Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin"