From: | "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz> |
---|---|
To: | <josh(at)agliodbs(dot)com> |
Cc: | "Kris Jurka" <books(at)ejurka(dot)com>, "PostgreSQL - JDBC" <pgsql-jdbc(at)postgresql(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Subject: | Re: JDBC, prepared queries, and partitioning |
Date: | 2008-02-13 22:33:25 |
Message-ID: | F0238EBA67824444BC1CB4700960CB4804A4F6C4@dmpeints002.isotach.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Josh Berkus wrote
> 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?
8.3 server release notes mention a couple of options:
- Automatically re-plan cached queries when table definitions change or statistics are updated (Tom)
- Implement new commands DISCARD ALL, DISCARD PLANS, DISCARD TEMPORARY, CLOSE ALL, and DEALLOCATE ALL (Marko Kreen, Neil)
I've no idea about the extent of that first one, but perhaps you could include a tiny table in the query, and update statistics on the table.
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please advise by reply immediately, destroy it and do not copy, disclose or use it in any way.
__________________________________________________________________
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Denne | 2008-02-13 22:38:27 | Re: JDBC, prepared queries, and partitioning |
Previous Message | Simon Riggs | 2008-02-13 22:32:45 | Re: JDBC, prepared queries, and partitioning |