| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hooks |
| Date: | 2016-12-27 21:44:07 |
| Message-ID: | c2d0fc4d-780e-e075-db62-8382fe9ebc49@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/27/16 1:43 PM, David Fetter wrote:
>> So I'm a bit suspicious of this project in the first place, but it's
>> hard to discuss which hooks should be documented when you haven't
>> defined what you mean by documentation.
> I haven't quite come up with that, but I'd pictured a part of the SGML
> docs that goes over, at a minimum, what all the hooks are and what
> they do, at least at the level of a sentence or paragraph's worth of
> description.
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.
--
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 | Fabien COELHO | 2016-12-27 21:45:02 | Re: BUG: pg_stat_statements query normalization issues with combined queries |
| Previous Message | Jim Nasby | 2016-12-27 21:41:46 | Re: pg_stat_activity.waiting_start |