Re: parameterized limit statements

> >                                 ^^
> > If I hardcode $5 to any sub-ridiculous value, I get a proper index
plan.
> > Does your patch assume a limit of 1 or 10% of table rows?
>
> If it doesn't have a value for the parameter, it'll assume 10% of
table
> rows, which is what it's done for a long time if the LIMIT isn't
> reducible to a constant.
>
> I suspect the real issue here is that whatever you are doing doesn't
> give the planner a value to use for the parameter.  IIRC, at the
moment
> the only way that that happens is if you use the unnamed-statement
> variation of the Parse/Bind/Execute protocol.

hm...I'm using named statements over ExecPrepared.  I can also confirm
the results inside psql with prepare/execute.  I can send you a test
case, but was just wondering if your change to makelimit was supposed to
address this case.

Merlin