Message-ID: <43D13217.2030704@zg.htnet.hr>
Date: Fri, 20 Jan 2006 19:55:19 +0100
From: Rikard Pavelic <rikard.pavelic@zg.htnet.hr>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Stored procedures
References: <6.2.1.2.0.20060120120150.08ab7b00@localhost>
	<20060120172026.GF20182@pervasive.com>
	<25978.1137783074@sss.pgh.pa.us>
In-Reply-To: <25978.1137783074@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>
>> 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