Quick Links

Re: JDBC, prepared queries, and partitioning

From:	Josh Berkus <josh(at)agliodbs(dot)com>
To:	Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc:	Stephen Denne <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, Kris Jurka <books(at)ejurka(dot)com>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject:	Re: JDBC, prepared queries, and partitioning
Date:	2008-02-13 22:23:23
Message-ID:	200802131423.24613.josh@agliodbs.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-jdbc

> > If the wild variations don't affect the cost estimate, they won't
> > affect the plan?
>
> Cost estimates are made at planning time. If you don't replan, no, they
> won't.

So, just to confirm: there is no way with v3 to make it not use a cached
plan, either on 8.2 or 8.3, correct?

Can I use v2 against 8.3?

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Re: JDBC, prepared queries, and partitioning at 2008-02-13 21:55:56 from Simon Riggs

Responses

Re: JDBC, prepared queries, and partitioning at 2008-02-13 22:29:08 from Kris Jurka
Re: JDBC, prepared queries, and partitioning at 2008-02-13 22:33:25 from Stephen Denne
Re: JDBC, prepared queries, and partitioning at 2008-02-13 22:55:05 from Oliver Jowett

Browse pgsql-jdbc by date

	From	Date	Subject
Next Message	Kris Jurka	2008-02-13 22:29:08	Re: JDBC, prepared queries, and partitioning
Previous Message	Kris Jurka	2008-02-13 22:15:10	Re: JDBC, prepared queries, and partitioning