From: Rikard Pavelic <rikard.pavelic@zg.htnet.hr>
To: pgsql-performance@postgresql.org
Subject: Re: Stored procedures
Date: Fri, 20 Jan 2006 19:55:19 +0100
Message-ID: <43D13217.2030704@zg.htnet.hr> (raw)
In-Reply-To: <25978.1137783074@sss.pgh.pa.us>
References: <6.2.1.2.0.20060120120150.08ab7b00@localhost>
<20060120172026.GF20182@pervasive.com>
<25978.1137783074@sss.pgh.pa.us>
>
>> Hi,
>>
>> Will simple queries such as "SELECT * FROM blah_table WHERE tag='x';
>> work any
>> faster by putting them into a stored procedure?
>
> IMHO no, why do you think so? You can use PREPARE instead, if you have
> many
> selects like this.
I tought that creating stored procedures in database means
storing it's execution plan (well, actually storing it like a
compiled object). Well, that's what I've learned couple a years
ago in colledge ;)
What are the advantages of parsing SP functions every time it's called?
My position is that preparing stored procedures for execution solves
more problems, that it creates.
And the most important one to be optimizing access to queries from
multiple connections (which is one of the most important reasons for
using stored procedures in the first place).
Best regards,
Rikard
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: rikard.pavelic@zg.htnet.hr
Subject: Re: Stored procedures
In-Reply-To: <43D13217.2030704@zg.htnet.hr>
* 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