Re: proposal: alternative psql commands quit and exit

From: Everaldo Canuto <everaldo(dot)canuto(at)gmail(dot)com>
To: Vladimir Svedov <vodevsh(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Daniel Vérité <daniel(at)manitou-mail(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: proposal: alternative psql commands quit and exit
Date: 2017-12-08 16:32:08
Message-ID: CACYgWU=Ee77PGqUseMAnDWMFaewwigteUya4tozwEb3i3X9c+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 8, 2017 at 2:26 PM, Vladimir Svedov <vodevsh(at)gmail(dot)com> wrote:

> I wonder if *exit;* to terminate loop be confused with exit psql in case
> of bad syntax. then instead of reporting error in plpgsql it would just
> silently exit?..
>

I just tested it and works as expected. Second line of patch takes care of
it:

if (pset.cur_cmd_interactive && query_buf->len == 0 &&

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Ford 2017-12-08 16:47:55 Re: proposal: alternative psql commands quit and exit
Previous Message Vladimir Svedov 2017-12-08 16:26:46 Re: proposal: alternative psql commands quit and exit