Re: First feature patch for plperl - draft [PATCH] - Mailing list pgsql-hackers

Robert Haas <robertmhaas@gmail.com> writes:
> So, do we look for another way to provide the functionality besides
> having a GUC, or is the functionality itself bad?

I don't think we want random Perl code running inside the postmaster,
no matter what the API to cause it is.  I might hold my nose for "on
load" code if it can only run in backends, though I still say that
it's a badly designed concept because of the uncertainty about who
will run what when.  Shlib load time is not an event that ought to be
user-visible.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Block-level CRC checks
Next
From: "David E. Wheeler"
Date:
Subject: Re: First feature patch for plperl - draft [PATCH]