| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | "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 17:01:25 |
| Message-ID: | 18fd2734-ea43-cb51-a5aa-59ecb0e9f353@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-12-28 17:01:53 | Re: Hooks |
| Previous Message | Tom Lane | 2016-12-28 17:00:43 | Re: Reporting planning time with EXPLAIN |