Re: non-deterministic error related to MIN/MAX optimization - Mailing list pgsql-bugs

From Jeff Davis
Subject Re: non-deterministic error related to MIN/MAX optimization
Date
Msg-id 1219726185.8211.11.camel@jdavis
Whole thread Raw
In response to Re: non-deterministic error related to MIN/MAX optimization  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: non-deterministic error related to MIN/MAX optimization
List pgsql-bugs
On Mon, 2008-08-25 at 22:26 -0400, Tom Lane wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
> > => select max(a), generate_series(1,2) as g from foo order by g desc;
> > ERROR:  set-valued function called in context that cannot accept a set
>
> This strikes me as a pretty useless query, so the fact that it doesn't
> work doesn't bother me.  It's mostly accidental that there are any
> variants that do work, I think.  Why would you want a SRF in a sort key?

The following line was added to the regression tests:

aggregates.sql:226:
select max(unique2), generate_series(1,3) as g from tenk1 order by g
desc;

I have no argument with what you say above. But one of my colleagues at
Truviso was doing some experiments, and it was causing a regression
failure here. I should have been more clear.

So if it truly is a useless query, shouldn't we at least remove the
regression test?

Regards,
    Jeff Davis

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4374: pg_restore does not restore public schema comment
Next
From: Tom Lane
Date:
Subject: Re: non-deterministic error related to MIN/MAX optimization