PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16333
PG Version9.6.17
OSWindows 10
Opened2020-04-01 23:26:29+00
Reported byTyler Reynolds
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16333
Logged by:          Tyler Reynolds
Email address:      (redacted)
PostgreSQL version: 9.6.17
Operating system:   Windows 10
Description:        

To reproduce:

CREATE DATABASE test;
CREATE EXTENSION citext;

SELECT position('foo'::citext IN 'Foobar'::citext) =
strpos('Foobar'::citext, 'foo'::citext) as "positionEqualsStrpos";

Expected: "positionEqualsStrpos" returns TRUE.
Actual: "positionEqualsStrpos" returns FALSE.

Citext does not create an overload for position() supporting citext
parameters, therefore position(a in b) always runs case-sensitive.

Messages

DateAuthorSubject
2020-04-01 23:26:29+00PG Bug reporting formBUG #16333: position() function not equivalent to strpos() function when comparing citext
2020-04-02 01:00:17+00"David G(dot) Johnston"Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
2020-04-02 01:04:44+00Tom LaneRe: BUG #16333: position() function not equivalent to strpos() function when comparing citext
2020-04-02 20:53:17+00Peter EisentrautRe: BUG #16333: position() function not equivalent to strpos() function when comparing citext
2020-04-02 21:46:06+00Tom LaneRe: BUG #16333: position() function not equivalent to strpos() function when comparing citext
2020-04-05 10:41:51+00Peter EisentrautRe: BUG #16333: position() function not equivalent to strpos() function when comparing citext