From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: Hans Buschmann <buschmann@nidsa.net>,
        PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17842: Adding a qual to a working query gets bogus syntax
 error
In-reply-to: 
 <CAKFQuwZeb+TFWNsaX3Mo8g3qK8AA_Fdzw+wjpKakx4Siq_oCWQ@mail.gmail.com>
References: <17842-0697f895ced573ee@postgresql.org>
 <2692255.1678810846@sss.pgh.pa.us>
 <dd6cfce2fca54079b1ad7cd044ee4b38@nidsa.net>
 <CAKFQuwZeb+TFWNsaX3Mo8g3qK8AA_Fdzw+wjpKakx4Siq_oCWQ@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Tue, 14 Mar 2023 11:19:32 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2757853.1678818318.1@sss.pgh.pa.us>
Date: Tue, 14 Mar 2023 14:25:18 -0400
Message-ID: <2757854.1678818318@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2757854.1678818318%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tue, Mar 14, 2023, 11:12 Hans Buschmann <buschmann@nidsa.net> wrote:
>> 2. Why is it reporting an syntax error (supposed at parse time) and not a
>> runtime error (supposed at execution time)

> Your parsed query doesn't have a syntax error.  Data it processes does,
> which is found when parsing that data during query execution.

Right.  It's kind of unfortunate perhaps that we use SQLSTATEs from
the "syntax error" class for malformed data input, but that seems
unlikely to change.  In any case, it's pretty obvious that this error
is not complaining about anything in the text of the query.

			regards, tom lane