Commits

DateSubjectAuthorReleases
2010-10-28 Fix plpgsql's handling of "simple" expression evaluation. Tom Lane 8.2.19
2010-08-09 Modify the handling of RAISE without parameters so that the error it throws Tom Lane 9.1.0
2010-01-19 Add "USING expressions" option to plpgsql's OPEN cursor FOR EXECUTE. Tom Lane 9.0.0
2010-01-10 Improve plpgsql's handling of record field references by forcing all potential Tom Lane 9.0.0
2009-11-13 Add control knobs for plpgsql's variable resolution behavior, and make the Tom Lane 9.0.0
2009-11-12 Remove plpgsql's separate lexer (finally!), in favor of using the core lexer Tom Lane 9.0.0
2009-11-10 More incremental refactoring in plpgsql: get rid of gram.y dependencies on Tom Lane 9.0.0
2009-11-09 Modernize plpgsql's handling of parse locations, making it look a lot more Tom Lane 9.0.0
2009-11-07 Rearrange plpgsql parsing to simplify and speed it up a bit. Tom Lane 9.0.0
2009-11-06 Change plpgsql from using textual substitution to insert variable references Tom Lane 9.0.0
2009-11-05 Remove plpgsql's RENAME declaration, which has bizarre and mostly nonfunctional Tom Lane 9.0.0
2009-11-04 Add support for invoking parser callback hooks via SPI and in cached plans. Tom Lane 9.0.0
2009-09-29 Allow MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE BACKWARD ALL Tom Lane 9.0.0
2009-09-22 Implement the DO statement to support execution of PL code without having Tom Lane 9.0.0
2009-04-19 Rethink the idea of having plpgsql depend on parser/gram.h. Aside from the Tom Lane 8.4.0
2009-04-19 Revise plpgsql's scanner to process comments and string literals in a way Tom Lane 8.4.0
2009-04-09 Fix the plpgsql memory leak exhibited in bug #4677. That leak was introduced Tom Lane 8.4.0
2009-01-07 Fix executor/spi.h to follow our usual conventions for include files, ie, Tom Lane 8.4.0
2008-11-05 Rename several aliases for PLpgSQL_datum.dno to also be called dno. Tom Lane 8.4.0
2008-10-09 Fix overly tense optimization of PLpgSQL_func_hashkey: we must represent Tom Lane 8.0.19
2008-10-09 Fix overly tense optimization of PLpgSQL_func_hashkey: we must represent Tom Lane 8.1.15
2008-10-09 Fix overly tense optimization of PLpgSQL_func_hashkey: we must represent Tom Lane 8.2.11
2008-10-09 Fix overly tense optimization of PLpgSQL_func_hashkey: we must represent Tom Lane 8.3.5
2008-10-09 Fix overly tense optimization of PLpgSQL_func_hashkey: we must represent Tom Lane 8.4.0
2008-05-15 Support SQL/PSM-compatible CASE statement in plpgsql. Tom Lane 8.4.0