Re: Prepared Statement Query Planning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Brett Henderson <brett(at)bretth(dot)com>
Cc: Віталій Тимчишин <tivv00(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Prepared Statement Query Planning
Date: 2009-08-29 14:52:45
Message-ID: 25520.1251557565@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-jdbc

Brett Henderson <brett(at)bretth(dot)com> writes:
> However I don't think it will work in my case. I currently have three
> different ways of selecting records, 1. by timestamp range (as in my
> initial example), 2. by records in a temp table, and 3. unrestricted.
> The unrestricted example isn't an issue because a full table scan is
> appropriate in that case. However the temp table one is a different
> matter.

In the case of a temp table you have to ANALYZE the temp table after
filling it; otherwise the planner is working completely blind as to
what is in it. (autovacuum will not do this for you...)

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Віталій Тимчишин 2009-08-29 18:05:27 Re: Prepared Statement Query Planning
Previous Message Brett Henderson 2009-08-29 12:40:36 Re: Prepared Statement Query Planning