From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca> |
Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: psql misbehaves because of a simple typo |
Date: | 2001-12-02 15:16:12 |
Message-ID: | 21089.1007306172@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca> writes:
> Is it me (who hasn't read some FAQ or a doc/man page) or
> it's a bug in the psql interactive terminal?
Both. There's a bug there, but it's not the one you think.
psql seems to forget that it's got unmatched parentheses in the
buffer after executing a \? command. Watch the prompt:
regression=# (select
regression(# \?
... yadda yadda ...
regression-# 2;
ERROR: parser: parse error at or near ";"
regression=# (select
regression(# \?
... yadda yadda ...
regression-# 2);
?column?
----------
2
(1 row)
In the first example, it should not have thought that it had
a complete command after "2;".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | matthew green | 2001-12-02 15:32:15 | Re: Second call for platform testing |
Previous Message | Tom Lane | 2001-12-02 15:11:27 | Re: Yet more logging questions |