> -----Original Message-----
> From: Tom Lane
>
> I said:
> > "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> >> I thought that the problem was, that you cannot simply skip the
> >> insert, because at that time the tuple (pointer) might have already
> >> been successfully inserted into an other index/heap, and thus this was
> >> only sanely possible with savepoints/undo.
>
> > Hmm, good point.  If we don't error out the transaction then that tuple
> > would become good when we commit.  This is nastier than it appears.
>
> On further thought, I think it *would* be possible to do this without
> savepoints,

It's a very well known issue that the partial rolloback functionality is
a basis of this kind of problem and it's the reason I've mentioned that
UNDO functionality has the highest priority. IMHO we shouldn't
implement a partial rolloback functionality specific to an individual
problem.

regards,
Hiroshi Inoue

In response to

• Re: Bulkloading using COPY - ignore duplicates? at 2001-10-01 17:21:41 from Tom Lane

pgsql-hackers by date

Next:	From: Thomas Lockhart	Date: 2001-10-01 21:01:10
	Subject: Re: cvs tip problems
Previous:	From: Bruce Momjian	Date: 2001-10-01 20:57:25
	Subject: Re: CVS changes