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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: why does plperl cache functions using just a bool for is_trigger
Дата
Msg-id 8029.1288801722@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: why does plperl cache functions using just a bool for is_trigger  (Alex Hunsaker <badalex@gmail.com>)
Ответы Re: why does plperl cache functions using just a bool for is_trigger  (Alex Hunsaker <badalex@gmail.com>)
Список pgsql-hackers
Alex Hunsaker <badalex@gmail.com> writes:
> On Mon, Nov 1, 2010 at 16:59, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Surely, removing the internal name's dependency on the istrigger flag is
>> wrong.  If you're going to maintain separate hash entries at the pltcl
>> level, why would you want to risk collisions underneath that?

> Good catch.  I was basing it off plperl which uses the same proname
> for both (sprintf(subname, %s__%u", prodesc->proname, fn_oid)).  Its
> OK for plperl because when we compile we save a reference to it and
> use that directly (more or less).  The name does not really matter.

OK, applied.

I notice that plpython is also using the trigger relation's OID, but I
don't know that language well enough to tell whether it really needs to.
        regards, tom lane


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

Предыдущее
От: Dimitri Fontaine
Дата:
Сообщение: Re: ALTER OBJECT any_name SET SCHEMA name
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Fwd: Re: ALTER OBJECT any_name SET SCHEMA name