BUG #15084: Invalid LIKE pattern not always reported - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #15084: Invalid LIKE pattern not always reported
Date
Msg-id 151941775547.1463.3686411361406861190@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #15084: Invalid LIKE pattern not always reported  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: BUG #15084: Invalid LIKE pattern not always reported  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      15084
Logged by:          Tudor Bosman
Email address:      tudorb@gmail.com
PostgreSQL version: 9.5.11
Operating system:   Ubuntu 16.04
Description:

PostgreSQL will not always detect an invalid LIKE pattern (one that ends
with a backslash).

Example:

tudor=# select 'foo' like 'foo\';
 ?column?
----------
 f
(1 row)

tudor=# select 'foobar' like 'foo\';
ERROR:  LIKE pattern must not end with escape character

This probably happens because the pattern is only parsed lazily (as needed);
if PostgreSQL detects that a match is impossible, it doesn't even look at
the rest of the pattern.

Still, it would be nice for error reporting to be consistent.

Thanks,
-Tudor.


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15082: PostgreSQL 11 dev bug with window range partition by QUERY
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #15084: Invalid LIKE pattern not always reported