From cc510d97afe63cacb3129d4bd19b14118cada6bb Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 3 Jun 2013 14:19:32 -0400 Subject: Add semicolons to eval'd strings to hide a minor Perl behavioral change. "eval q{foo}" used to complain that the error was on line 2 of the eval'd string, because eval internally tacked on "\n;" so that the end of the erroneous command was indeed on line 2. But as of Perl 5.18 it more sanely says that the error is on line 1. To avoid Perl-version-dependent regression test results, use "eval q{foo;}" instead in the two places where this matters. Per buildfarm. Since people might try to use newer Perl versions with older PG releases, back-patch as far as 9.0 where these test cases were added. --- src/pl/plperl/sql/plperl_init.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/pl/plperl/sql/plperl_init.sql') diff --git a/src/pl/plperl/sql/plperl_init.sql b/src/pl/plperl/sql/plperl_init.sql index d60268d033e..4ebf3f86eb7 100644 --- a/src/pl/plperl/sql/plperl_init.sql +++ b/src/pl/plperl/sql/plperl_init.sql @@ -3,7 +3,7 @@ -- This test tests setting on_plperl_init after loading plperl LOAD 'plperl'; -SET SESSION plperl.on_plperl_init = ' system("/nonesuch") '; +SET SESSION plperl.on_plperl_init = ' system("/nonesuch"); '; SHOW plperl.on_plperl_init; -- cgit v1.2.3