pgsql: Keep plperl's current_call_data record on the stack, instead of - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Keep plperl's current_call_data record on the stack, instead of
Date
Msg-id E1TCDSs-0005Zn-Nh@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Keep plperl's current_call_data record on the stack, instead of palloc'ing.

This at least saves some palloc overhead, and should furthermore reduce
the risk of anything going wrong, eg somebody resetting the context the
current_call_data record was in.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/9afc6481117d2dd936e752da0424a2b6b05f6459

Modified Files
--------------
src/pl/plperl/plperl.c |   42 +++++++++++++++++++-----------------------
1 files changed, 19 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix case of window function + aggregate + GROUP BY expression.
Next
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: Fixed some connection leaking tests.