From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | haddock(at)mail(dot)ru |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8117: simple but huge query infinite execution time |
Date: | 2013-04-25 15:12:53 |
Message-ID: | 24342.1366902773@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
haddock(at)mail(dot)ru writes:
> query has the following scheme
> SELECT
> regexp_matches('...',' (\d+)\:','g'),
> regexp_matches('...','\:([\d\.]+)','g')
I'm not sure what you're expecting this to do, but what it will actually
do is produce a number of rows equal to the least common multiple of the
periods of the two set-returning functions. In this example it seems
the first call produces 2510 rows and the second 2507 rows. Those
numbers have no factors in common, so you get 6292570 rows, the same as
if you'd written "select * from regexp_matches(...), regexp_matches(...)".
In short, I see no bug here. The behavior of queries with multiple SRFs
in the same targetlist is a bit dubious, but we're not going to change
it, except perhaps by deprecating such usages altogether.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2013-04-25 17:07:12 | Re: BUG #8114: Peer authentication in cgi-perl |
Previous Message | haddock | 2013-04-25 14:38:30 | BUG #8117: simple but huge query infinite execution time |