Skip site navigation (1) Skip section navigation (2)

Re: Bulkloading using COPY - ignore duplicates?

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bulkloading using COPY - ignore duplicates?
Date: 2001-10-01 21:25:41
Message-ID: 3705826352029646A3E91C53F7189E320167AE@sectorbase2.sectorbase.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-10-01 21:38:24
Subject: Re: Bulkloading using COPY - ignore duplicates?
Previous:From: Bruce MomjianDate: 2001-10-01 21:22:58
Subject: Re: cvs problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group