Re: Bulkloading using COPY - ignore duplicates? - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject Re: Bulkloading using COPY - ignore duplicates?
Date
Msg-id 3705826352029646A3E91C53F7189E320167AF@sectorbase2.sectorbase.com
Whole thread Raw
In response to Bulkloading using COPY - ignore duplicates?  (Lee Kindness <lkindness@csl.co.uk>)
List pgsql-hackers
> > 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.

This problem could be solved now by implementing *single* trigger.
In future, we could give users ability to specify trigger
execution order.
But with proposed feature ...

> Mind you, I'm not actually advocating that we do any of this ;-).

I understand -:)

> I was just sketching a possible implementation approach in
> case someone wants to try it.

And I'm just sketching possible problems -:)

Vadim


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: cvs tip problems
Next
From: Tom Lane
Date:
Subject: Re: cvs problem