| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | wangchuanting <wangchuanting(at)huawei(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog |
| Date: | 2017-06-11 03:28:48 |
| Message-ID: | 20170611032848.xazvtrdyhruoxonq@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
wangchuanting wrote:
> we use Postgres-XC+pg10(4 coordinator + 4 datanode(pg 10 as datanode, and 1
> master 1 standby for each datanode)), and benchmark tpcc, there is some
> cross datanode transactions that use 2pc, during testing, we restart the
> cluster, then one datanode standby can not recovery done and hangup with
> TwoPhaseStateLock deadlock.
>
> and sorry, we reinstall the cluster, and the log is removed, we will try to
> reproduce, but anyway, the code is not right like Michael saied.
Did you have any luck reproducing the original issue? It would be good
if you could confirm that the bug is gone with the patch I posted in
https://www.postgresql.org/message-id/20170611022536.goef4cdbmgicye5g@alvherre.pgsql
Thanks
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2017-06-11 15:52:55 | Re: BUG #14682: row level security not work with partitioned table |
| Previous Message | Alvaro Herrera | 2017-06-11 03:24:48 | Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-06-11 03:42:35 | Re: Make ANALYZE more selective about what is a "most common value"? |
| Previous Message | Alvaro Herrera | 2017-06-11 03:24:48 | Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog |