Re: psql does not provide proper response

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: Shaozhong SHI <shishaozhong(at)gmail(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: psql does not provide proper response
Date: 2022-01-20 18:54:04
Message-ID: CAFj8pRATHy1sJaO5G7-330E=S=xtLhh_VYrGJ_-BTUnEDj4Aog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

čt 20. 1. 2022 v 19:50 odesílatel Bryn Llewellyn <bryn(at)yugabyte(dot)com> napsal:

> > shishaozhong(at)gmail(dot)com wrote:
> >
> > I do not know what happened.
> >
> > psql does not provide proper response anymore.
> >
> > I typed the following and see nothing.
> >
> > user=# select * from boundaryline.scotland_and_wales_const_region
> > user-#
> >
> > Can anyone enlighten me?
>

you are missing to write semicolon - at end of command

you see it in prompt "-#"

Regards

Pavel

>
> This happens to me all too frequently. Then I kick myself and realize that
> I earlier said “\o spool.txt” (by hand) and forgot to turn it off with the
> bare “\o”. This is my typical use case:
>
> \o spool.txt
> \i script.sql
>
> The script causes an error. I read it, see the bad statement, and then
> type the correct statement by hand. Then I see what you did: a big fat
> nothing.
>
> Might this be happening to you?
>
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2022-01-20 18:54:52 Re: psql does not provide proper response
Previous Message David G. Johnston 2022-01-20 18:53:25 Re: [EXT] Re: Can we get the CTID value