Thread

1. Re: Bulkloading using COPY - ignore duplicates?

   Vadim Mikheev <vmikheev@sectorbase.com> — 2001-10-01T21:25:41Z

   > The effects don't stop propagating there, either. The decision
   > not to insert the tuple must be reported up still further, so
   > that the executor knows not to run any AFTER INSERT/UPDATE
   > triggers and knows not to count the tuple as inserted/updated
   > for the command completion report.
   
   But what about BEFORE insert/update triggers which could insert
   records too?
   
   Vadim
   
   

2. Re: Bulkloading using COPY - ignore duplicates?

   Tom Lane <tgl@sss.pgh.pa.us> — 2001-10-01T21:38:24Z

   "Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
   >> The effects don't stop propagating there, either. The decision
   >> not to insert the tuple must be reported up still further, so
   >> that the executor knows not to run any AFTER INSERT/UPDATE
   >> triggers and knows not to count the tuple as inserted/updated
   >> for the command completion report.
   
   > But what about BEFORE insert/update triggers which could insert
   > records too?
   
   Well, what about them?  It's already possible for a later BEFORE trigger
   to cause the actual insertion to be suppressed, so I don't see any
   difference from what we have now.  If a BEFORE trigger takes actions
   on the assumption that the insert will happen, it's busted already.
   
   
   Mind you, I'm not actually advocating that we do any of this ;-).
   I was just sketching a possible implementation approach in case someone
   wants to try it.
   
   			regards, tom lane