Re: [HACKERS] Why does plpython delay composite type resolution?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Why does plpython delay composite type resolution?
Дата
Msg-id 4841.1482331189@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Why does plpython delay composite type resolution?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: [HACKERS] Why does plpython delay composite type resolution?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 12/21/16 1:55 AM, Andreas Karlsson wrote:
>> Does your patch handle "ALTER TYPE name ADD ATTRIBUTE ..."? My immediate
>> guess would be that it could be a cache invalidation thing.

> Won't that only happen at end of transaction?

No.
BEGIN;SELECT plpython_function();ALTER TYPE ...;SELECT plpython_function();COMMIT;

For that matter, the plpython function could execute the ALTER itself
through SPI, or call another function that does so.

(I'm not claiming that the existing code, either in plpython or other
PLs, necessarily handles such all scenarios nicely.  But we shouldn't
make it worse.)
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Rethinking our fulltext phrase-search implementation
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Proposal : Parallel Merge Join