Re: [HACKERS] Hooks
От | Craig Ringer |
---|---|
Тема | Re: [HACKERS] Hooks |
Дата | |
Msg-id | CAMsr+YH-Z=S03Fj7pcOOGj3kuzXbGxEE+vbjP8M5oK7s16SUMA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Hooks (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
Ответы |
Re: [HACKERS] Hooks
|
Список | pgsql-hackers |
On 28 December 2016 at 12:15, Jim Nasby <Jim.Nasby@bluetreble.com> wrote: > Can we reduce the scope of this to a manageable starting point? I'm guessing > that all existing hooks share certain characteristics that it'd be pretty > easy to detect. If you can detect the hook (which I guess means finding a > static variable with hook in the name) then you can verify that there's an > appropriate comment block. I'm guessing someone familiar with tools like > doxygen could set that up without too much effort, and I'd be surprised if > the community had a problem with it. Lets just make sure the comment blocks are nice and grep-able too. I think this is a great idea FWIW. Discovering the extension points within Pg isn't easy. Callbacks aren't easy to find either. -- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: