"Petr Jelinek" <pjmo...@pjmodos.net> writes:
> I was wondering if maybe this could be split to 2 separate patches, one would
> be all the changes to the existing plpgsql code - rename delete_function to
> plpgsql_delete_function and extern plpgsql_delete_function,
> copy_plpgsql_datum, plpgsql_estate_setup, plpgsql_destroy_econtext and the
> other patch would be the actual checker.
> Reasoning for this is that the first patch (exporting some of plpgsql
> internals) should be very safe to commit and would be useful by itself even
> if the checker does not get in 9.3 since it would enable users to write
> lints/checkers/analysers for plpgsql as standalone extensions (for my use
> case this is actually way more useful than having the checker as part of
> core).
What exactly do you have in mind there? The way we load extensions,
they can't (AFAIK) see each other's defined symbols, so you couldn't
really make an independent extension that would call functions in
plpgsql. This is not really open for debate, either, as changing that
would risk creating symbol collisions between modules that never had to
worry about polluting global namespace before.
I would note also that we absolutely, positively do not guarantee not
to change plpgsql's private data structures in minor releases.
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
