On Dec 13, 2007, at 7:03 PM, Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)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
>> 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.
What do you think about adding type information to the log? Something
DETAIL: parameters: $1 = '21001'::integer, $2 = '2007-12-11
or similar would have revealed the source of my problem earlier.
In response to
pgsql-jdbc by date
|Next:||From: Tom Lane||Date: 2007-12-14 16:17:12|
|Subject: Re: Slow query after upgrades |
|Previous:||From: Albert László-Róbert||Date: 2007-12-14 11:39:21|
|Subject: Re: Slow query after upgrades|