Re: "stored procedures" - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: "stored procedures"
Date
Msg-id 4DB53C7C020000250003CC6E@gw.wicourts.gov
Whole thread Raw
In response to Re: "stored procedures"  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: "stored procedures"  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> wrote:
> Procedures unlike functions however can no longer rely that
> catalogs remain static visibility wise through execution for
> functions.
If you start from the perspective that stored procedures are in many
respects more like psql scripts than functions, this shouldn't be
too surprising.  If you have a psql script with multiple database
transactions, you know that other processes can change things
between transactions.  Same deal with SPs.
The whole raison d'être for SPs is that there are cases where people
need something *different* from functions.  While it would be *nice*
to leverage plpgsql syntax for a stored procedure language, if it
means we have to behave like a function, it's not worth it.
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: wrong hint message for ALTER FOREIGN TABLE
Next
From: Stephen Frost
Date:
Subject: Re: branching for 9.2devel