Thanks, Kris.
I remembr this thread. Searched the archives for a hint but found
nothing that could happen.
Your point is clear and I believe a local solution is the best answer
for this problem, be it messing around with planner settings or
by sending a "set enable_seqscan=false" to the backend.
>
>
> On Thu, 1 Apr 2004, Marcus Andree S. Magalhaes wrote:
>
>> Last one... This time, specifically to the java side: what
>> do you think about adding new methods, say, setEnableSeqScan(boolean)
>> and getEnableSeqScan() to our (by our I mean
>> postgres) drivers?
>>
>
> I don't see this as a useful general purpose method worth adding. What
> about all the other GUC parameters? There was a discussion a while ago
> about making these and other variables configurable through the
> connection URL or datasource, but that would be to establish defaults,
> not to modify it on the fly.
>
> http://archives.postgresql.org/pgsql-jdbc/2004-02/msg00022.php
>
> Kris Jurka
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
