Re: Trigger behaviour not as stated

2018-01-28 Thread Tom Lane
Bruce Momjian writes: > Oh, I am sorry. I was focused on the first part of the sentence and > didn't notice your change to the second part. How is this attachment? Seems same as your previous version? regards, tom lane

Re: Trigger behaviour not as stated

2018-01-28 Thread Bruce Momjian
On Sun, Jan 28, 2018 at 03:57:07PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > Uh, I don't think we want to highlight the statement vs row difference > > here but the fact that statement triggers fire on the referenced object > > and not on the effected rows. I have

Re: Trigger behaviour not as stated

2018-01-28 Thread Tom Lane
Bruce Momjian writes: > Uh, I don't think we want to highlight the statement vs row difference > here but the fact that statement triggers fire on the referenced object > and not on the effected rows. I have attached an updated patch which I > think is an improvement

Re: Trigger behaviour not as stated

2018-01-28 Thread Bruce Momjian
On Sun, Jan 28, 2018 at 02:18:38PM -0500, Tom Lane wrote: > Thomas Munro writes: > > On Thu, Jan 25, 2018 at 11:07 AM, Bruce Momjian wrote: > >> ... The attached patch updates the docs to say > >> statement-level triggers fire on the "referenced"

Re: Trigger behaviour not as stated

2018-01-28 Thread Tom Lane
Thomas Munro writes: > On Thu, Jan 25, 2018 at 11:07 AM, Bruce Momjian wrote: >> ... The attached patch updates the docs to say >> statement-level triggers fire on the "referenced" table, while row-level >> triggers fire only on the "affected"

Re: Trigger behaviour not as stated

2018-01-28 Thread Thomas Munro
On Thu, Jan 25, 2018 at 11:07 AM, Bruce Momjian wrote: > On Wed, Jan 24, 2018 at 01:10:08PM -0500, Bruce Momjian wrote: >> On Wed, Nov 29, 2017 at 07:39:34PM +, i...@thepathcentral.com wrote: >> > The following documentation comment has been logged on the website: >> > >> >