From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inline PL/pgSQL |
Date: | 2005-05-09 18:08:13 |
Message-ID: | 200505091108.13767.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jonah,
> In addition to package support in plpgsql, it would be really handy to
> have inline plpgsql. Likewise, I think there are others who feel this
> way as-well.
I think a number of people would be interested in this. However, your
biggest development issue, as I've been told, is that the Pl/pgSQL parser
isn't nearly as mature as the SQL parser. So an overhaul of the PL/pgSQL
backend code would need to precede any merger of the two parsers.
Also, take a look at the "pl/pgsql enabled by default" thread on this mailing
list for security concerns. These security concerns would be much more
significant if plpgsql were automatically available on the command line. As
such, you'd need to make building it in to the SQL command line a
compile-time option so that security-conscious admins could disable it if
they want to.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-05-09 18:18:10 | Re: Inline PL/pgSQL |
Previous Message | Joshua D. Drake | 2005-05-09 17:58:27 | Re: Inline PL/pgSQL |