oat_post_create expected behavior

Поиск
Список
Период
Сортировка
От Mary Xu
Тема oat_post_create expected behavior
Дата
Msg-id CAHoZxqvN2eoic_CvjsAvpryyLyA2xG8JmsyMtKFFJz_1oFhfOg@mail.gmail.com
обсуждение исходный текст
Ответы Re: oat_post_create expected behavior
Список pgsql-hackers
Hello,

I was using an object access hook for oat_post_create access while creating an extension and expected that I would be able to query for the newly created extension with get_extension_oid(), but it was returning InvalidOid. However, the same process works for triggers, so I was wondering what the expected behavior is? 
From the documentation in objectaccess.h, it doesn't mention anything about CommandCounterIncrement() for POST_CREATE which implied to me that it wasn't something I would need to worry about. 
One option I thought of was this patch where CCI is called before the access hook so that the new tuple is visible in the hook. Another option would be to revise the documentation to reflect the expected behavior. 

Thanks,

Mary Xu
Вложения

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