From: Tom Lane <tgl@sss.pgh.pa.us>
To: buschmann@nidsa.net
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17842: Adding a qual to a working query gets bogus syntax
 error
In-reply-to: <17842-0697f895ced573ee@postgresql.org>
References: <17842-0697f895ced573ee@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 14 Mar 2023 15:48:29 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2692254.1678810846.1@sss.pgh.pa.us>
Date: Tue, 14 Mar 2023 12:20:46 -0400
Message-ID: <2692255.1678810846@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2692255.1678810846%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> During refactoring our application I got a bogus syntax error when adding a
> simple where-clause to a working query.

My guess is that this:

> ('0'||split_part(split_part(nline,'(',2),')',1))::smallint as nlen

sometimes produces a string that fails to cast to smallint, which you
accidentally don't notice because it never gets evaluated for troublesome
values of nline --- until you add the "nlen > 0" condition.  There isn't
anything in your query that prevents that from being evaluated fairly
early.

This isn't a bug, or at least you have provided no data that would
motivate (or indeed allow) anyone else to poke into it more closely.

			regards, tom lane