From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Jeff Certain <gcertain(at)dynamicsignal(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: regexp_matches bug in 9.3.4 and 9.4.1 |
Date: | 2015-05-04 23:51:22 |
Message-ID: | 16889.1430783482@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Seems the however the citext version of regexp_matches is invoked it
> ignores the global flag. Haven't explored deeper.
Hm ...
regression=# create extension citext;
CREATE EXTENSION
regression=# \df regexp_matches
List of functions
Schema | Name | Result data type | Argument data types | Type
------------+----------------+------------------+----------------------+--------
pg_catalog | regexp_matches | SETOF text[] | text, text | normal
pg_catalog | regexp_matches | SETOF text[] | text, text, text | normal
public | regexp_matches | text[] | citext, citext | normal
public | regexp_matches | text[] | citext, citext, text | normal
(4 rows)
Looks like somebody just fat-fingered the declaration of citext's
regexp_matches() functions: they should be marked proretset and
they ain't. Sigh. I wonder if any of the other ones are wrong.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-05-05 01:03:57 | Re: Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated) |
Previous Message | David G. Johnston | 2015-05-04 22:59:30 | Re: regexp_matches bug in 9.3.4 and 9.4.1 |