"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> "Affan Salman" <affan(at)enterprisedb(dot)com> writes:
>> With some time to spare, I thought I'd submit a quick-fix patch to the
>> issue I reported here:
> I don't think this is right. If the original tuple was inserted by a
> subtransaction of our transaction, it will have been checked at
> subtransaction subcommit, no?
That doesn't sound right.
> RELEASE SAVEPOINT destroys a savepoint previously defined in the current
> Destroying a savepoint makes it unavailable as a rollback point, but it has
> no other user visible behavior.
On the other hand what happens if you have constraints not deferred, insert a
record, then set constraints deferred and update it?
In response to
pgsql-patches by date
|Next:||From: Stephan Szabo||Date: 2007-07-16 06:58:49|
|Subject: Re: Deferred RI trigger for non-key UPDATEs and subxacts|
|Previous:||From: Greg Smith||Date: 2007-07-16 04:28:55|
|Subject: Re: HOT latest patch - version 8|