Skip site navigation (1) Skip section navigation (2)

Re: Prepare Statement

From: Kris Jurka <books(at)ejurka(dot)com>
To: Jie Liang <jie(at)stbernard(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Prepare Statement
Date: 2004-06-18 21:47:01
Message-ID: Pine.BSO.4.56.0406181645280.21687@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbcpgsql-sql

On Fri, 18 Jun 2004, Jie Liang wrote:

> However, I am still thinking if I call one SELECT and one DELECT and one
> UPDATE and one INSERT a thousand times against same table with different
> arguments, should I consider performance iusse?

Right, this is a case where some benefits can be found, but remember the 
premature optimization adage.

> 
> Secondly, I assume the function should be a pre-compiled object stored
> on server side, doesn't it.
> 

I depends on the language the function is written.  plpgsql caches plans, 
but not all procedural languages do.

Kris Jurka

In response to

pgsql-sql by date

Next:From: Kris JurkaDate: 2004-06-18 21:47:53
Subject: Re: Prepare Statement
Previous:From: Jaime CasanovaDate: 2004-06-18 21:38:28
Subject: case stement when null

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-06-18 21:47:53
Subject: Re: Prepare Statement
Previous:From: Kris JurkaDate: 2004-06-18 18:49:16
Subject: Re: proposal for CallableStatements to handle multiple out

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group