pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Event Triggers: adding information
Date: Wed, 23 Jan 2013 15:04:43 -0500
Message-ID: <20130123200443.GI23670@momjian.us> (raw)
In-Reply-To: <CA+Tgmobzi9pDqWAtx_QfVq=JnP28kxW9camcuv3SGY=79D4nSQ@mail.gmail.com>
References: <CA+TgmoZYFhn=DyenBLr8KUZXYHtgjo-O8YE-7y61WKR6F05UQA@mail.gmail.com>
	<m21udesaz3.fsf@2ndQuadrant.fr>
	<CA+TgmoZPhj6Rw-DottwresCJnOmRewbOxp2AABwyxP2k7vZf-Q@mail.gmail.com>
	<m2622pmnnn.fsf@2ndQuadrant.fr>
	<m2vcapl7tl.fsf@2ndQuadrant.fr>
	<CA+TgmoYgpub59RrQ+n=qoejmADhj-kppCfDgQjWP+rR+8m+39Q@mail.gmail.com>
	<m2zk00cjbz.fsf@2ndQuadrant.fr>
	<CA+TgmobaY1gsMW1_cbKKoYA1j5vd8Yx_eWN98-4apAMzj_tZcQ@mail.gmail.com>
	<20130123193618.GA29229@momjian.us>
	<CA+Tgmobzi9pDqWAtx_QfVq=JnP28kxW9camcuv3SGY=79D4nSQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Wed, Jan 23, 2013 at 03:02:24PM -0500, Robert Haas wrote:
> On Wed, Jan 23, 2013 at 2:36 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > On Wed, Jan 23, 2013 at 09:33:58AM -0500, Robert Haas wrote:
> >> On Wed, Jan 23, 2013 at 4:57 AM, Dimitri Fontaine
> >> <dimitri@2ndquadrant.fr> wrote:
> >> > Thanks for commiting the fixes. About the regression tests, I think
> >> > you're right, but then I can't see how to include such a test. Maybe you
> >> > could add the other one, though?
> >>
> >> Can you point me specifically at what you have in mind so I can make
> >> sure I'm considering the right thing?
> >>
> >> > +1 for this version, thanks.
> >>
> >> OK, committed that also.
> >
> > Also, I assume we no longer want after triggers on system tables, so I
> > removed that from the TODO list and added event triggers as a completed
> > item.
> 
> Seems reasonable.  Event triggers are not completed in the sense that
> there is a lot more stuff we can do with this architecture, but we've
> got a basic implementation now and that's progress.  And they do
> address the use case that triggers on system tables would have
> targeted, I think, but better.

Right.  Users would always be chasing implementation details if they
tried to trigger on system tables.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (114+ messages)  latest in thread

Message-ID: <20130123200443.GI23670@momjian.us>
Permalink:  ../20130123200443.GI23670@momjian.us/
Also on:    postgresql.org/message-id/20130123200443.GI23670@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, robertmhaas@gmail.com, dimitri@2ndquadrant.fr, alvherre@2ndquadrant.com
  Subject: Re: Event Triggers: adding information
  In-Reply-To: <20130123200443.GI23670@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox