Fix plpgsql regression test
authorPavan Deolasee <pavan.deolasee@gmail.com>
Tue, 29 Aug 2017 10:24:45 +0000 (15:54 +0530)
committerPavan Deolasee <pavan.deolasee@gmail.com>
Tue, 29 Aug 2017 10:24:45 +0000 (15:54 +0530)
commit5c03f66df4a31344eaea5bdbf041ae3472056202
tree51e458c179917793ef2ee5187744555d9787ed25
parent3913cead822f6498d85ed6f3a21b0ef80d5d24cc
Fix plpgsql regression test

There were two broad categories of problems.

1. Errors due to lack of savepoint support
2. Errors and side effects due to lack of trigger support.

For 1, we reorganised the test case so that they can be run without savepoint.
For 2, we mostly accepted the regression changes. Apart from usual errors while
creating/dropping triggers, there were differences in query results because
of changes to preceding update/insert/delete statements. The behaviour of those
statements change because of lack of triggers.
src/test/regress/expected/plpgsql.out
src/test/regress/sql/plpgsql.sql