Re: Initial refactoring of plperl.c [PATCH]

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Initial refactoring of plperl.c [PATCH]
Date: 2009-11-28 14:35:10
Message-ID: 4B11351E.6050001@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tim Bunce wrote:
> - Changed MULTIPLICITY check from runtime to compiletime.
> No loads the large Config module.
>

ISTM the trouble with this is that it assumes that the library that we
compile with is the same as the library loaded at runtime. But there is
no guarantee of that at all.

Perhaps we could do this at library load time, so if it's preloaded in
the postmaster we don't have to rerun the check for every backend.

Have you measured the cost involved here? Are we really saving that much?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-28 18:59:14 Re: Writeable CTE patch
Previous Message Jeff Davis 2009-11-28 03:18:20 Re: operator exclusion constraints