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

From Tsunakawa, Takayuki
Subject Re: [HACKERS] Hooks
Date
Msg-id 0A3221C70F24FB45833433255569204D1F66D6CC@G01JPEXMBYT05
Whole thread Raw
In response to Re: [HACKERS] Hooks  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Hooks  (David Fetter <david@fetter.org>)
List pgsql-hackers
From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Jim Nasby
> AFAIK there's no way to get a list of hooks today, short of something like
> `git grep hook`. I think a simple list of what hooks we have, when they
> fire and where to find them in code would be sufficient.

How about putting a descriptive comment at the location where each hook variable is defined, using some convention
(e.g.like Javadoc-style)?  A separate document such as README and wiki can fail to be updated.  OTOH, if someone wants
toadd a new hook, we can expect him to add appropriate comment by following existing hooks.  Using a fixed tag, e.g.
"<Hook>",would facilitate finding all hooks.
 

Regards
Takayuki Tsunakawa






pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] BUG: pg_stat_statements query normalization issues with combined queries
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] ALTER TABLE parent SET WITHOUT OIDS and the oid column