X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 6557252849
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 21 Jun 2005 16:46:49 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 87998-08
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 21 Jun 2005 19:46:47 +0000 (GMT)
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197])
	by svr1.postgresql.org (Postfix) with ESMTP id 8386E52847
	for <pgsql-performance@postgresql.org>;
	Tue, 21 Jun 2005 16:46:46 -0300 (ADT)
Received: by wproxy.gmail.com with SMTP id 37so231928wra
	for <pgsql-performance@postgresql.org>;
	Tue, 21 Jun 2005 12:46:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
	b=tO9voMqeQkKm1E1BD8U/fUwnzd6O+SCLuip2Y/D+Ll3zdEAtNOmZSLGrce9XSJSq8+xr3KRqijTSTJtzYxkGMnlnkWI8pSJxuLNS02WdhF4aLsEHQpyVftSffvrCbUf36aJaFAJy1+FVT3m1CAaSuDpp6pmrdOsQBCnpeqXbblg=
Received: by 10.54.2.42 with SMTP id 42mr3392770wrb;
	Tue, 21 Jun 2005 12:46:04 -0700 (PDT)
Received: by 10.54.150.13 with HTTP; Tue, 21 Jun 2005 12:46:03 -0700 (PDT)
Message-ID: <1efd553a05062112462c30e9ff@mail.gmail.com>
Date: Tue, 21 Jun 2005 15:46:03 -0400
From: Oliver Crosby <ryusei@gmail.com>
Reply-To: Oliver Crosby <ryusei@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Prepared statements vs. Stored Procedures
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1417_11666427.1119383163975"
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.32 tagged_above=0 required=5 tests=HTML_10_20,
	HTML_MESSAGE, RCVD_BY_IP
X-Spam-Level: 
X-Archive-Number: 200506/409
X-Sequence-Number: 13046

------=_Part_1417_11666427.1119383163975
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I'm hoping someone can offer some advice here.
 I have a large perl script that employs prepared statements to do all its=
=20
queries. I'm looking at using stored procedures to improve performance time=
s=20
for the script. Would making a stored procedure to replace each prepared=20
statement be worthwhile? If not, when could I use stored procedures to=20
improve performance?
 Thanks in advance.

------=_Part_1417_11666427.1119383163975
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>I'm hoping someone can offer some advice here.</div>
<div>&nbsp;</div>
<div>I have a large perl script that employs prepared statements to do all =
its queries. I'm looking at using stored procedures to improve performance =
times for the script. Would making a stored procedure to replace each prepa=
red statement be worthwhile? If not, when could I use stored procedures to =
improve performance?
</div>
<div>&nbsp;</div>
<div>Thanks in advance.</div>

------=_Part_1417_11666427.1119383163975--