Re: [HACKERS] Hooks - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] Hooks
Date
Msg-id CAMsr+YH-Z=S03Fj7pcOOGj3kuzXbGxEE+vbjP8M5oK7s16SUMA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Hooks  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Hooks
List 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 by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Hooks
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Some thoughts about multi-server sync rep configurations