Re: why does plperl cache functions using just a bool for is_trigger - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: why does plperl cache functions using just a bool for is_trigger
Date
Msg-id AANLkTi=h08oKqOF1kQE6UdiuDCFzW61CzbQ5p_Zmcfoj@mail.gmail.com
Whole thread Raw
In response to Re: why does plperl cache functions using just a bool for is_trigger  (Alex Hunsaker <badalex@gmail.com>)
List pgsql-hackers
On Mon, Nov 1, 2010 at 15:24, Alex Hunsaker <badalex@gmail.com> wrote:
houldn't cache any of the setup but just redo it all every time.
>
> Huh?  I might try and argue that if the new test was more complex than
> 2 compares :P.  In-fact the way it stands now we uselessly grab the
> functions pg_proc entry in the common case.

This is bogus, I missed the fact that we need it to make sure the
function is uptodate for the OR REPLACE in CREATE OR REPLACE.


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: why does plperl cache functions using just a bool for is_trigger
Next
From: Tom Lane
Date:
Subject: Re: SR fails to send existing WAL file after off-line copy