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

Re: why does plperl cache functions using just a bool for is_trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why does plperl cache functions using just a bool for is_trigger
Date: 2010-11-05 14:56:01
Message-ID: 23769.1288968961@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer(at)wulczer(dot)org> writes:
> PS: I'm wondering if there's any noticable slowdown from always starting
> a subxact before doing SPI. Plperl users seemed not to notice, so I
> guess I shouldn't worry.

It's not cheap :-( ... but it's *necessary*.  There's no other way to
get sane behavior.

If the cost annoys you, you should put some effort into making subxact
start/stop cheaper overall, rather than trying to avoid having one here.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-11-05 15:11:04
Subject: Re: ALTER TABLE ... IF EXISTS feature?
Previous:From: Tom LaneDate: 2010-11-05 14:49:36
Subject: Re: ALTER TABLE ... IF EXISTS feature?

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