In article <13289.1260290974@xxxxxxxxxxxxx>, Tom Lane <tgl@xxxxxxxxxxxxx> writes: > Julian Mehnle <julian@xxxxxxxxxx> writes: >> So far, so good. However, can someone please explain the following to me? >> wisu-dev=# SELECT regexp_matches('quux@foo@bar.zip', '([@.]|[^@.]+)+', 'g'); >> wisu-dev=# SELECT regexp_matches('quux@foo@bar.zip', '([@.]|[^@.]+){1,2}', 'g'); >> wisu-dev=# SELECT regexp_matches('quux@foo@bar.zip', '([@.]|[^@.]+){1,3}', 'g'); > These might be a bug, but the behavior doesn't seem to me that it'd be > terribly well defined in any case. The function should be pulling the > match to the parenthesized subexpression, but here that subexpression > has got multiple matches --- which one would you expect to get? Perl seems to return always the last one, but the last one is never just 'p' - so I also think that Julian has spotted a bug. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general