On Fri, Sep 15, 2017 at 8:43 AM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> Note that
> TransitionCaptureState already holds tuplestores for each operation
> (INSERT, UPDATE, DELETE)
Erm, that's not quite true -- it only separates INSERT and UPDATE for
now. It would need to be true, so it would need to gain one more to
have the full set.
> ... perhaps using a flag in the TransitionCaptureState to prevent multiple
> firings.
Of course that would need to be per-trigger, not just one flag per
TCS. Also the change in firing rules for multiply-referenced tables
would apply also when there are no TTs involved, so perhaps TCS is not
a good place for that state.
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs