Search Postgresql Archives

Re: XMIN semantic at peril ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Erik Jones <erik@xxxxxxxxxx> writes:
> If the query is always based on a primary key + XMIN, and since  
> vacuum is the only thing that sets FrozenTransactionId, would it be  
> unsane to change the update to

> - update row with "... where pk=... and XMIN IN (old_xmin_from_read,
> FrozenTransactionId)

I wouldn't risk it, because that *would* fail in the case Karsten
mentioned of an update sequence taking so long that a concurrent
update got frozen.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux