Re: Determining if a table really changed in a trigger

Hi! On Sat, Nov 6, 2021 at 2:43 PM Tom Lane wrote: > Mitar writes: > > Anyone? Any way to determine the number of affected rows in a statement > > trigger? > > Check the size of the transition relation. Yes, this is what we are currently doing, but it looks very inefficient if you want just

Re: Determining if a table really changed in a trigger

Mitar writes: > Anyone? Any way to determine the number of affected rows in a statement > trigger? Check the size of the transition relation. regards, tom lane

Re: Question: Is it possible to get the new xlog position after query execution?

On 2021-11-01 00:36:16 -0400, Oleg Serov wrote: > On Sun, Oct 31, 2021 at 4:29 PM Peter J. Holzer wrote: > > On 2021-10-29 13:22:56 -0400, Oleg Serov wrote: > > We are using a master/slave replication system where we perform > > writes on master and use replication to offload reads.

Re: Determining if a table really changed in a trigger

Hi! On Wed, Oct 27, 2021 at 12:46 AM Mark Dilger wrote: > I felt the same way about it, but after glancing quickly through the code and > docs nothing jumped out. The information is clearly available, as it gets > returned at the end of the UPDATE statement in the "UPDATE 0" OR "UPDATE 3", >