From: | Tom Duffey <tduffey(at)techbydesign(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Slow query after upgrades |
Date: | 2007-12-13 22:58:32 |
Message-ID: | 0116C2A9-8DB5-4EBE-A66B-BE7F2A11651C@techbydesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Dec 13, 2007, at 4:52 PM, Guillaume Smet wrote:
> It's not an EXPLAIN ANALYZE so we can't see if the query is slow or
> fast.
QUERY PLAN
-------------------------------------------------------------------------------------------------------------------------------------------------
Index Scan Backward using point_history_pkey on point_history
(cost=0.00..264.60 rows=58 width=20) (actual time=0.131..1.596
rows=192 loops=1)
Index Cond: ((point_id = 21001) AND ("timestamp" >= '2007-12-11
22:22:45'::timestamp without time zone))
Total runtime: 1.846 ms
> If it's fast using the parameters in psql, just try to add
> protocolVersion=2 to your JDBC connection URL as I told you earlier.
> It should solve your problem. You won't be able to use new features of
> protocol v3 but if you used 7.4 before, it shouldn't be a problem for
> you.
This makes a huge difference, thanks. However, is there anything I
can do to help improve the performance of that query when using a
newer protocol?
Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2007-12-13 23:05:46 | Re: Slow query after upgrades |
Previous Message | Guillaume Smet | 2007-12-13 22:52:45 | Re: Slow query after upgrades |