Re: [PERFORMANCE] Stored Procedures

From: Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORMANCE] Stored Procedures
Date: 2006-01-20 18:50:23
Message-ID: 43D130EF.3010205@zg.htnet.hr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2006-01-20 18:51:14 Re: SELECT MIN, MAX took longer time than SELECT COUNT, MIN, MAX
Previous Message Antoine 2006-01-20 18:32:34 query stopped working after tables > 50000 records