From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Volkan YAZICI" <yazicivo(at)ttmail(dot)com> |
Cc: | depesz(at)depesz(dot)com, "Harald Fuchs" <hari(dot)fuchs(at)googlemail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: generate_series woes |
Date: | 2008-04-16 13:01:10 |
Message-ID: | b42b73150804160601s4cf90b5at337331d320ac3398@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Apr 16, 2008 at 8:37 AM, Volkan YAZICI <yazicivo(at)ttmail(dot)com> wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > i think it would be better off not to limit some functionality for
> > builtin functions. it would be much nicer to have the ability to hint
> > planer about rowcount from function *in* the sql.
> >
> > something like:
> >
> > select i from generate_series(1,10) {hint:10} as i;
> >
> > i'm not proposiung syntax. i'm suggesting the functionality.
>
> I'm strongly declined for such non-SQL compliant solutions. I'd be
> appreciated if hackers can solve the problem internally, without bugging
> SQL syntax.
maybe -- just an idle thought -- the 'ROWS' clause of create function
could be expanded to take a simple expression based on the input
parameters.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2008-04-16 13:11:15 | Re: Master-master replication with PostgreSQL |
Previous Message | Julio Cesar Sánchez González | 2008-04-16 12:47:38 | Re: Master-master replication with PostgreSQL |