On Thursday, August 30, 2012 06:09:43 PM Andres Freund wrote:
> On Thursday, August 30, 2012 06:06:59 PM Robert Haas wrote:
> > On Thu, Aug 30, 2012 at 10:36 AM, Miroslav Šimulčík
> >
> > wrote:
> > > is there any way to check if row have already been modified by the
> > > current transaction? I
Robert Haas writes:
> On Thu, Aug 30, 2012 at 10:36 AM, Miroslav Å imulÄÃk
> wrote:
>> is there any way to check if row have already been modified by the current
>> transaction? I tried condition txid_current() = xmin, but there is problem
>> with the savepoints. After every savepoint rows are
On Thursday, August 30, 2012 06:06:59 PM Robert Haas wrote:
> On Thu, Aug 30, 2012 at 10:36 AM, Miroslav Šimulčík
>
> wrote:
> > is there any way to check if row have already been modified by the
> > current transaction? I tried condition txid_current() = xmin, but there
> > is problem with the s
On Thu, Aug 30, 2012 at 10:36 AM, Miroslav Šimulčík
wrote:
> is there any way to check if row have already been modified by the current
> transaction? I tried condition txid_current() = xmin, but there is problem
> with the savepoints. After every savepoint rows are getting higher xmin
> values, b
Hi,
is there any way to check if row have already been modified by the current
transaction? I tried condition txid_current() = xmin, but there is problem
with the savepoints. After every savepoint rows are getting higher xmin
values, but txid_current() remains the same.
Regards,
Miroslav Simulcik
