Pavel Stehule <pavel.steh...@gmail.com> writes:
> I propose a enhance the PLpgSQL_plugin struct by a new hook
> void (*pragma)(PLpgSQL_execstate *estate, PLpgSQL_pragma
> *pragma_stmt)
I repeat what I said a couple of days ago: it's a very bad idea to be
enabling more plpgsql plugins as long as the infrastructure can only
support one. We need to fix that *first* before we go merrily designing
more.
I don't like the notion of a pragma statement in this form anyway,
because you've essentially made it an executable statement; usually
pragmas are compile-time things. It appears to me that you've basically
commandeered the word "pragma" for "SET affecting a plugin's variable".
If we're inventing new callbacks for plugins, why not one that will extend
an existing statement having the right kind of semantics? Or actually,
why would it not be better for the plugin to be using a custom GUC for
its variable? There's a large amount of infrastructure that custom GUCs
can take advantage of, which you'd otherwise have to reinvent piece
by piece.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
