Re: BUG #7520: regexp_matches does not work as expected - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #7520: regexp_matches does not work as expected
Date
Msg-id 4119.1346819748@sss.pgh.pa.us
Whole thread Raw
In response to BUG #7520: regexp_matches does not work as expected  (sbasurto@soft-gator.com)
List pgsql-bugs
sbasurto@soft-gator.com writes:
> I am using regexp_matches in a function like this
> create or replace function test (v_string       in text)
> returns varchar as $$
> declare
> i_strings               text[];
> i_string                text[];

> i_strings :=
> regexp_matches(v_string,E'[a-zA-Z0-9:\\s\\-\\.#%]*:[A-Za-z0-9\\s\\-\\.#%]+','g');

> postgresql complains:
> ERROR:  query "SELECT
> regexp_matches(v_string,E'[a-zA-Z0-9:\\s\\-\\.#%]*:[A-Za-z0-9\\s\\-\\.#%]+','g')"
> returned more than one row

As per David Johnston's response on pgsql-general, this isn't a bug:
simple assignments in plpgsql expect a simple source value, not a rowset.

Personally I'd just iterate over the regexp_matches result directly and
not bother trying to store it into a variable, for example

    for string_var in select regexp_matches(...) loop ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Dave Vitek
Date:
Subject: windows 8 RTM compatibility issue (could not reserve shared memory region for child)
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #7519: incresed data base size and query performance lost