|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|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?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> I'm not sure about ripping it out, it does not sound like a good idea to
> me. It needs some addition and C level examples yes. The plan was to
> build a contrib module as an example, that would cancel any (supported)
> command you try to run by means of ereport(ERROR, );. Then add that in
> pieces in the docs with details about what's going on.
> While the commit fest was still running didn't look like the right time
> to work on that. Beta looks like when to be working on that.
> What do you think about the proposal here?
We're not adding new contrib modules during beta. Expanding the
documentation seems like a fine beta-period activity, though.
regards, tom lane
|Next Message||Robert Haas||2013-04-17 14:45:35||Re: erroneous restore into pg_catalog schema|
|Previous Message||Robert Haas||2013-04-17 13:57:02||Re: [sepgsql 2/3] Add db_schema:search permission checks|