From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Rohit_Behl <Rohit_Behl@infosys.com>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Jdbc/postgres performance
Date: Wed, 18 Oct 2006 13:51:47 +0100
Message-ID: <45362363.2060904@enterprisedb.com> (raw)
In-Reply-To: <407937EC76157D439EB0C9F9B6047EFD40017E@BLRKECMSG04.ad.infosys.com>
References: <407937EC76157D439EB0C9F9B6047EFD40017D@BLRKECMSG04.ad.infosys.com>
<407937EC76157D439EB0C9F9B6047EFD40017E@BLRKECMSG04.ad.infosys.com>
Rohit_Behl wrote:
> Hi
>
> I made the following changes to the conf file:
>
> enable_indexscan = true
>
> enable_seqscan = false
>
> We also have a large amount of data being inserted into our tables. I was just wondering if this could have an impact on the inserts since I guess this change is on the database.
enable_seqscan shouldn't affect plain inserts, but it will affect
*every* query in the system.
I would suggest using setting "prepareThreshold=0" in the JDBC driver
connection URL, or calling pstmt.setPrepareThreshold(0) in the
application. That tells the driver not to use server-side prepare, and
the query will be re-planned every time you execute it with the real
values of the parameters.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: heikki@enterprisedb.com, Rohit_Behl@infosys.com, mmoncure@gmail.com
Subject: Re: Jdbc/postgres performance
In-Reply-To: <45362363.2060904@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox