From: | David Goodenough <david(dot)goodenough(at)btconnect(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Does preparing statements other than selects help performance? |
Date: | 2005-08-05 09:08:42 |
Message-ID: | 200508051008.42597.david.goodenough@btconnect.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I was looking at an application recently which was written in Java and used
Postgresql as it DB. In it extensive use had been made of PreparedStatements
both for SELECTs and for INSERT, UPDATE and DELETE statements. Some of
the routines had multiple UPDATEs doing much the same thing but with
slightly different parameters. In the comments it was stated that it was
better to prepare lots of statements in advance rather than build one on the
spot (and then prepare it, it needed the substitution) because of the
optimiser.
This set me thinking (always dangerous). I can see how a SELECT can be
helped by preparing the statement, but not really how an INSERT could
or, other than the SELECT implicit in the WHERE clause on an UPDATE or
DELETE, how UPDATE or DELETE statements would be helped.
Can anyone enlighten me please?
David
From | Date | Subject | |
---|---|---|---|
Next Message | go | 2005-08-05 09:13:35 | Re: Weird lock or bug maybe? |
Previous Message | Zlatko Matić | 2005-08-05 08:59:57 | Re: Instalation batch file |