From: | "Rohit_Behl" <Rohit_Behl(at)infosys(dot)com> |
---|---|
To: | <heikki(at)enterprisedb(dot)com>, <mmoncure(at)gmail(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | |
Date: | 2006-10-19 12:36:52 |
Message-ID: | 407937EC76157D439EB0C9F9B6047EFD40017F@BLRKECMSG04.ad.infosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi
Thanks everybody. I have confirmed that this does not affect inserts. But the query performance has improved a lot.
Regards
Rohit
-----Original Message-----
From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Heikki Linnakangas
Sent: 18 October 2006 13:52
To: Rohit_Behl
Cc: Merlin Moncure; pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Jdbc/postgres performance
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
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
From | Date | Subject | |
---|---|---|---|
Next Message | Jens Schipkowski | 2006-10-19 12:38:54 | DB Performance decreases due to often written/accessed table |
Previous Message | Ioana Danes | 2006-10-19 11:43:55 | Re: Postgresql 8.1.4 - performance issues for select on |