Skip site navigation (1) Skip section navigation (2)

pgsql: Keep plperl's current_call_data record on the stack,instead of

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Keep plperl's current_call_data record on the stack,instead of
Date: 2012-09-13 17:44:34
Message-ID: E1TCDSs-0005Zn-Nh@gemulon.postgresql.org (view raw, whole thread or download thread mbox)
Thread:
Lists: 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

Next:From: User FxjrDate: 2012-09-14 02:07:37
Subject: npgsql - Npgsql2: Fixed some connection leaking tests.
Previous:From: Tom LaneDate: 2012-09-13 15:32:53
Subject: pgsql: Fix case of window function + aggregate + GROUP BY expression.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group