Re: Event Triggers reduced, v1

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndQuadrant.com>

To: Dimitri Fontaine <dfontaine@hi-media.com>

Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2012-06-15T22:30:27Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Replace int2/int4 in C code with int16/int32
- b8b2e3b2deea 9.3.0 cited

On 15 June 2012 21:27, Dimitri Fontaine <dfontaine@hi-media.com> wrote:

> The goal for this first patch is to avoid semantics issues so that we
> can get something technically clean in, and have more time to talk
> semantics next times. The main discussion to avoid is deciding if we
> want to fire event triggers for CREATE SEQUENCE and CREATE INDEX in a
> command that just did implement a SERIAL PRIMARY KEY in a table.

So this patch triggers once per top level command, just with
information about the set of nested events?

I'm happy if we make sweeping initial points like "don't generate
events for sequences and indexes" in the first version. We can always
add more later.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services