Hooks

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Hooks
Date: 2016-12-27 18:16:28
Message-ID: 20161227181628.GA9335@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Folks,

One of our hidden treasures is the hook system, documented only in
random presentations, if you can find them, and in the source code, if
you know to look.

I'd like to document the hooks that we consider public APIs.

To do this, I need to figure out whether there are hooks that we don't
consider public APIs, ideally in some principled way. C doesn't have
affordances built in for this, but maybe we've done something else to
indicate which are implementation details and which are public APIs.

Are there any hooks I should not document? If so, how will I tell in
the future that a new hook shouldn't be documented?

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Responses

  • Re: Hooks at 2016-12-27 18:32:46 from Tom Lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-12-27 18:23:03 Re: BUG: pg_stat_statements query normalization issues with combined queries
Previous Message Magnus Hagander 2016-12-27 18:12:31 Re: Support for pg_receivexlog --format=plain|tar