Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
d6375d61
Commit
d6375d61
authored
Jul 13, 2005
by
Neil Conway
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation for some new PL/Perl features. Patch from David Fetter,
various editorialization from Neil Conway.
parent
b4363b77
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
81 additions
and
17 deletions
+81
-17
doc/src/sgml/plperl.sgml
doc/src/sgml/plperl.sgml
+81
-17
No files found.
doc/src/sgml/plperl.sgml
View file @
d6375d61
<!--
$PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.4
1 2005/06/05 03:16:29 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.4
2 2005/07/13 02:10:42 neilc
Exp $
-->
<chapter id="plperl">
...
...
@@ -54,6 +54,33 @@ $$ LANGUAGE plperl;
</programlisting>
The body of the function is ordinary Perl code.
</para>
<para>
As with ordinary Perl code, you should use the strict pragma,
which you can do in one of two ways:
<itemizedlist>
<listitem>
<para>
Globally, by adding <quote>plperl</quote> to the list of <xref
linkend="guc-custom-variable-classes"> and setting
<literal>plperl.use_strict</literal> to true in
<filename>postgresql.conf</filename>
</para>
</listitem>
<listitem>
<para>
One function at a time, by using PL/PerlU (you must be database
superuser to do this) and including
<programlisting>
use strict;
</programlisting>
in the function body.
</para>
</listitem>
</itemizedlist>
</para>
<para>
The syntax of the <command>CREATE FUNCTION</command> command requires
...
...
@@ -117,6 +144,20 @@ $$ LANGUAGE plperl;
function is strict or not.
</para>
<para>
Perl can return <productname>PostgreSQL</productname> arrays as
references to Perl arrays. Here is an example:
<programlisting>
CREATE OR REPLACE function returns_array()
RETURNS text[][] AS $$
return [['a"b','c,d'],['e\\f','g']];
$$ LANGUAGE plperl;
select returns_array();
</programlisting>
</para>
<para>
Composite-type arguments are passed to the function as references
to hashes. The keys of the hash are the attribute names of the
...
...
@@ -158,18 +199,47 @@ SELECT * FROM perl_row();
</para>
<para>
PL/Perl functions can also return sets of either scalar or composite
types. To do this, return a reference to an array that contains
either scalars or references to hashes, respectively. Here are
some simple examples:
PL/Perl functions can also return sets of either scalar or
composite types. In general, you'll want to return rows one at a
time both to speed up startup time and to keep from queueing up
the entire result set in memory. You can do this with
<function>return_next</function> as illustrated below. Note that
after the last <function>return_next</function>, you must put
either <literal>return;</literal> or (better) <literal>return
undef;</literal>
<programlisting>
CREATE OR REPLACE FUNCTION perl_set_int(int) RETURNS SETOF INTEGER AS $$
return [0..$_[0]];
CREATE OR REPLACE FUNCTION perl_set_int(int)
RETURNS SETOF INTEGER AS $$
foreach (0..$_[0]) {
return_next($_);
}
return undef;
$$ LANGUAGE plperl;
SELECT * FROM perl_set_int(5);
CREATE OR REPLACE FUNCTION perl_set()
RETURNS SETOF testrowperl AS $$
return_next({ f1 => 1, f2 => 'Hello', f3 => 'World' });
return_next({ f1 => 2, f2 => 'Hello', f3 => 'PostgreSQL' });
return_next({ f1 => 3, f2 => 'Hello', f3 => 'PL/Perl' });
return undef;
$$ LANGUAGE plperl;
</programlisting>
For small result sets, you can return a reference to an array that
contains either scalars, references to arrays, or references to
hashes for simple types, array types, and composite types,
respectively. Here are some simple examples of returning the entire
result set as a reference:
<programlisting>
CREATE OR REPLACE FUNCTION perl_set_int(int) RETURNS SETOF INTEGER AS $$
return [0..$_[0]];
$$ LANGUAGE plperl;
SELECT * FROM perl_set_int(5);
CREATE OR REPLACE FUNCTION perl_set() RETURNS SETOF testrowperl AS $$
return [
...
...
@@ -177,16 +247,11 @@ CREATE OR REPLACE FUNCTION perl_set() RETURNS SETOF testrowperl AS $$
{ f1 => 2, f2 => 'Hello', f3 => 'PostgreSQL' },
{ f1 => 3, f2 => 'Hello', f3 => 'PL/Perl' }
];
$$
LANGUAGE plperl;
$$ LANGUAGE plperl;
SELECT * FROM perl_set();
</programlisting>
When you do this, Perl will have to build the entire array in memory;
therefore the technique does not scale to very large result sets. You
can instead call <function>return_next</function> for each element of
the result set, passing it either a scalar or a reference to a hash,
as appropriate to your function's return type.
</para>
<para>
...
...
@@ -217,7 +282,7 @@ SELECT * FROM perl_set();
</para>
<para>
PL/Perl
itself presently
provides two additional Perl commands:
PL/Perl provides two additional Perl commands:
<variablelist>
<varlistentry>
...
...
@@ -281,7 +346,6 @@ INSERT INTO test (i, v) VALUES (3, 'third line');
INSERT INTO test (i, v) VALUES (4, 'immortal');
CREATE FUNCTION test_munge() RETURNS SETOF test AS $$
my $res = [];
my $rv = spi_exec_query('select i, v from test;');
my $status = $rv->{status};
my $nrows = $rv->{processed};
...
...
@@ -289,9 +353,9 @@ CREATE FUNCTION test_munge() RETURNS SETOF test AS $$
my $row = $rv->{rows}[$rn];
$row->{i} += 200 if defined($row->{i});
$row->{v} =~ tr/A-Za-z/a-zA-Z/ if (defined($row->{v}));
push @$res, $row
;
return_next($row)
;
}
return
$res
;
return
undef
;
$$ LANGUAGE plperl;
SELECT * FROM test_munge();
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment