| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| 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 16:30:23 |
| Message-ID: | CADkLM=fEFM5sAoi2p+jx_A_wEHYpBmvfbHwpvbUEyP2wpOKCXA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 22, 2016 at 10:08 AM, Daniel Verite <daniel(at)manitou-mail(dot)org>
wrote:
> 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
>
>
Yes, I would like it to honor ON_ERROR_STOP. I'll look into that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-02-22 17:47:25 | Re: psql metaqueries with \gexec |
| Previous Message | Andres Freund | 2016-02-22 16:11:41 | Re: checkpointer continuous flushing - V18 |