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

From Jim Nasby
Subject Re: [HACKERS] Hooks
Date
Msg-id 18fd2734-ea43-cb51-a5aa-59ecb0e9f353@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] Hooks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/27/16 11:14 PM, David Fetter wrote:
> Sure, but that seems like an effort somewhat orthogonal to the one I
> proposed, which is to get some user-facing i.e. SGML docs up for the
> current hooks.

My point was that a (presumably small) amount of effort towards 
earmarking hooks in code so that a tool can find them would be a step in 
the direction of allowing documentation to be generated direct from 
code, which several people agreed would be very worthwhile.

Is that effort *required* to meet your goal? No.

Does the journey of 1,000 miles start with a single step? Yes. So if 
there's a reasonably easy way to start that journey here, please 
consider doing so.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Reporting planning time with EXPLAIN
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Hooks