| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Reg Me Please" <regmeplease(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Variable LIMIT and OFFSET in SELECTs |
| Date: | 2007-11-15 12:56:59 |
| Message-ID: | 162867790711150456ga08c48dwe92bb8ea4410da4c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello
LIMIT has impact on execution plan, so there cannot be variables. Use
SRF function and dynamic statements instead.
Regards
Pavel
On 15/11/2007, Reg Me Please <regmeplease(at)gmail(dot)com> wrote:
> In any case, what'd be the benefit for not allowing "variables" as LIMIT and
> OFFSET argument?
>
> --
> Reg me Please
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abraham, Danny | 2007-11-15 13:09:10 | Chunk Delete |
| Previous Message | Reg Me Please | 2007-11-15 12:50:34 | Re: Variable LIMIT and OFFSET in SELECTs |