Re: On conflict update & hint bits - Mailing list pgsql-hackers

From Tom Lane
Subject Re: On conflict update & hint bits
Date
Msg-id 20872.1477313084@sss.pgh.pa.us
Whole thread Raw
In response to Re: On conflict update & hint bits  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
Konstantin Knizhnik <k.knizhnik@postgrespro.ru> writes:
> Just for information: I know that you are working on this issue, but as
> far as we need to proceed further with our testing of multimaster,
> I have done the following obvious changes and it fixes the problem (at
> least this assertion failure is not happen any more):

This seems kind of the hard way --- why didn't you put the buffer lock
calls into ExecCheckHeapTupleVisible?

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f1fb7d621b0e6bd2eb0ba2ac9634c5b5a03564b
        regards, tom lane



pgsql-hackers by date:

Previous
From: Victor Wagner
Date:
Subject: Re: Patch: Implement failover on libpq connect level.
Next
From: Alvaro Herrera
Date:
Subject: Re: issue with track_commit_timestamp and server restart