From: Marcos <mjs_ops@gmx.net>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Rikard Pavelic <rikard.pavelic@zg.htnet.hr>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORMANCE] Stored Procedures
Date: Mon, 23 Jan 2006 08:14:14 +0000
Message-ID: <1138004054.949.10.camel@servidor> (raw)
In-Reply-To: <20060120213455.GT20182@pervasive.com>
References: <43D130EF.3010205@zg.htnet.hr>
<20060120191031.GO20182@pervasive.com>
<43D13C2F.1030203@zg.htnet.hr>
<20060120213455.GT20182@pervasive.com>
Em Sex, 2006-01-20 às 15:34 -0600, Jim C. Nasby escreveu:
> On Fri, Jan 20, 2006 at 08:38:23PM +0100, Rikard Pavelic wrote:
> > This would solve problems with prepare which is per session, so for
> > prepared function to be
> > optimal one must use same connection.
>
> If you're dealing with something that's performance critical you're not
> going to be constantly re-connecting anyway, so I don't see what the
> issue is.
This one was my doubt, perhaps in based desktop applications this is
true, but in web applications this is not the re-connecting is
constant :(.
Then the preprare not have very advantage because your duration is per
session.
Marcos.
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: mjs_ops@gmx.net, jnasby@pervasive.com, rikard.pavelic@zg.htnet.hr
Subject: Re: [PERFORMANCE] Stored Procedures
In-Reply-To: <1138004054.949.10.camel@servidor>
* 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