| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Kevin Grittner <kgrittn(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: On conflict update & hint bits |
| Date: | 2016-10-24 12:44:44 |
| Message-ID: | 20872.1477313084@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-10-24 12:52:16 | Re: issue with track_commit_timestamp and server restart |
| Previous Message | Victor Wagner | 2016-10-24 11:09:57 | Re: Patch: Implement failover on libpq connect level. |