| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hooks |
| Date: | 2016-12-28 04:19:11 |
| Message-ID: | CAMsr+YH-Z=S03Fj7pcOOGj3kuzXbGxEE+vbjP8M5oK7s16SUMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 December 2016 at 12:15, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-12-28 04:26:40 | Re: Some thoughts about multi-server sync rep configurations |
| Previous Message | Jim Nasby | 2016-12-28 04:15:55 | Re: Hooks |