From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Corey Huinker" <corey(dot)huinker(at)gmail(dot)com> |
Cc: | "Jim Nasby" <Jim(dot)Nasby(at)bluetreble(dot)com>,"PostgreSQL" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql metaqueries with \gexec |
Date: | 2016-02-22 15:08:23 |
Message-ID: | cbf9a1c4-8229-4303-9b17-61a6f3314cbd@mm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Corey Huinker wrote:
> ...and query text visibility, and result visibility, and error handling,
> etc. In this case, we're leveraging the psql environment we'd already set
> up, and if there's an error, \set ECHO queries shows us the errant SQL as
> if we typed it ourselves..
BTW, about error handling, shouldn't it honor ON_ERROR_STOP ?
With the patch when trying this:
=> set ON_ERROR_STOP on
=> select * from (values ('select 1/0', 'select 1/0')) AS n \gexec
it produces two errors:
ERROR: division by zero
ERROR: division by zero
I'd rather have the execution stop immediately after the first error,
like it's the case with successive queries entered normally via the
query buffer:
=> \set ON_ERROR_STOP on
=> select 1/0; select 1/0;
ERROR: division by zero
as opposed to:
=> \set ON_ERROR_STOP off
=> select 1/0; select 1/0;
ERROR: division by zero
ERROR: division by zero
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-02-22 15:29:33 | Re: Writing new unit tests with PostgresNode |
Previous Message | Tom Lane | 2016-02-22 15:07:37 | Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |