From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "David Christensen" <david(at)endpoint(dot)com>, "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: "stored procedures" |
Date: | 2011-04-25 14:18:52 |
Message-ID: | 4DB53C7C020000250003CC6E@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2011-04-25 14:19:00 | Re: branching for 9.2devel |
Previous Message | Tom Lane | 2011-04-25 14:17:45 | Re: wrong hint message for ALTER FOREIGN TABLE |