> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org [mailto:pgsql-hackers-
> owner@postgresql.org] On Behalf Of Pavel Stehule
> Sent: 28 November 2012 11:07
> To: Selena Deckelmann
> Cc: PostgreSQL Hackers
> Subject: Re: [HACKERS] plpgsql_check_function - rebase for 9.3
>
> Hello
>
> a some updated version
>
> * possibility to raise (and filter) performance warnings - detects IO castings
> * detects assign composite value to scalar variable
>
Hello,
I was wondering if maybe this could be split to 2 separate patches, one would be all the changes to the existing
plpgsqlcode - 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
wouldbe useful by itself even if the checker does not get in 9.3 since it would enable users to write
lints/checkers/analysersfor plpgsql as standalone extensions (for my use case this is actually way more useful than
havingthe checker as part of core).
Regards
Petr