Oliver Jowett <oliver@opencloud.com> writes:
> The JDBC driver is using an unnamed statement in this case, shouldn't
> the planner end up using index selectivity estimates based on the actual
> parameter values?
If he's using a recent enough backend, it should.
> From the explain output that just came through it looks like a type
> mismatch problem on the timestamp parameter.
Yeah, no question. Implicit casts to text strike again :-(. He was
probably getting the wrong answers, not only a slow query.
regards, tom lane
