From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: event trigger API documentation? |
Date: | 2013-04-18 15:04:27 |
Message-ID: | 20130418150427.GB2246@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dimitri Fontaine escribió:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Offhand, that seems about enough, but I'm just beginning to explore.
>
> I'm interested into hearing about any such use case…
>
> > Chances are, event triggers will end up somewhere near the top of the
> > release announcements, so we should have a consistent message about what
> > to do with them and how to use them. If for now, we say, we only
> > support writing them in PL/pgSQL, and here is how to do that, and here
> > are some examples, that's fine. But currently, it's not quite clear.
>
> I would prefer that we're silent about them for another (couple of?)
> release,
You can be as much silent as you want in marketing materials (though
maybe Berkus will disagree with you about being silent there), but it is
not admissible to be silent in the documentation or pretend the feature
is not there. Whatever got committed, however small, needs to be
properly documented.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-04-18 15:13:05 | Re: event trigger API documentation? |
Previous Message | Bruce Momjian | 2013-04-18 15:01:47 | Re: Enabling Checksums |