Re: Playing with set returning functions in SELECT list - behaviour intended?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Playing with set returning functions in SELECT list - behaviour intended?
Date: 2009-06-16 14:06:54
Message-ID: 13656.1245161214@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> So it looks like the number of result rows is the least common multiple
> of the cardinalities of all columns in the select list.

It's always been that way. The lack of any obviously-sane way to
handle multiple SRFs in a targetlist is exactly why the feature is
looked on with disfavor.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-06-16 14:12:25 Re: pg_relation_size, relation does not exist
Previous Message Merlin Moncure 2009-06-16 13:17:21 Re: Trigger Function and backup