From: Kris Jurka <books@ejurka.com>
To: Jie Liang <jie@stbernard.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-jdbc@postgresql.org
Subject: Re: Prepare Statement
Date: Fri, 18 Jun 2004 16:47:01 -0500 (EST)
Message-ID: <Pine.BSO.4.56.0406181645280.21687@leary.csoft.net> (raw)
In-Reply-To: <E7E213858379814A9AE48CA6754F5ECB03451962@mail01.stbernard.com>
References: <E7E213858379814A9AE48CA6754F5ECB03451962@mail01.stbernard.com>
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
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-sql@postgresql.org
Cc: books@ejurka.com, jie@stbernard.com, pgsql-jdbc@postgresql.org
Subject: Re: Prepare Statement
In-Reply-To: <Pine.BSO.4.56.0406181645280.21687@leary.csoft.net>
* 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