pgsql: plperl: Allow conversion from perl to postgresql array in OUT
Log Message:
-----------
plperl:
Allow conversion from perl to postgresql array in OUT parameters. Second,
allow hash form output from procedures with one OUT argument.
Pavel Stehule
Modified Files:
--------------
pgsql/doc/src/FAQ:
FAQ_DEV.html (r1.111 -> r1.112)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ_DEV.html.diff?r1=1.111&r2=1.112)
pgsql/src/pl/plperl:
plperl.c (r1.113 -> r1.114)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r1=1.113&r2=1.114)
pgsql/src/pl/plperl/sql:
plperl.sql (r1.7 -> r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/sql/plperl.sql.diff?r1=1.7&r2=1.8)
momjian@postgresql.org (Bruce Momjian) writes:
pgsql/src/pl/plperl/sql:
plperl.sql (r1.7 -> r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/sql/plperl.sql.diff?r1=1.7&r2=1.8)
Shouldn't there be an 'expected' update to go with the test-file update?
The few buildfarm members that aren't dying because of the GUC patch are
failing on this one. I'd commit a fixed expected file if I could get
HEAD to work locally, but ...
regards, tom lane
Tom Lane wrote:
momjian@postgresql.org (Bruce Momjian) writes:
pgsql/src/pl/plperl/sql:
plperl.sql (r1.7 -> r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/sql/plperl.sql.diff?r1=1.7&r2=1.8)Shouldn't there be an 'expected' update to go with the test-file update?
The few buildfarm members that aren't dying because of the GUC patch are
failing on this one. I'd commit a fixed expected file if I could get
HEAD to work locally, but ...
OK, I have backed out both plperl patches and returned the email to the
patch queue.
(Strange both the guc and plperl patches didn't generate any warnings
here. I don't think I can test plperl here but I know the guc was
tested.)
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +