Re: Initial refactoring of plperl.c [PATCH]

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Initial refactoring of plperl.c [PATCH]
Дата
Msg-id 4B11351E.6050001@dunslane.net
обсуждение исходный текст
Ответ на Initial refactoring of plperl.c [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Ответы Re: Initial refactoring of plperl.c [PATCH]
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jeff Davis
Дата:
Сообщение: Re: operator exclusion constraints
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Writeable CTE patch