|From:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|To:||Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>|
|Cc:||Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Ildar Musin <ildar(at)adjust(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>|
|Subject:||Re: Duplicated LSN in ReorderBuffer|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2019-Jul-09, Masahiko Sawada wrote:
> I think the cause of this bug would be that a ReorderBufferTXN entry
> of sub transaction is created as top-level transaction. And this
> happens because we skip to decode ASSIGNMENT during the state of
> snapshot builder < SNAPBUILD_FULL.
That explanation seems to make sense.
> Instead, I wonder if we can decode ASSIGNMENT even when the state of
> snapshot builder < SNAPBUILD_FULL_SNAPSHOT. That way, the
> ReorderBufferTXN entries of both top transaction and sub transaction
> are created properly before we decode NEW_CID.
Yeah, that seems a sensible remediation to me.
I would reduce the scope a little bit -- only create the assignment in
the BUILDING state, and skip it in the START state. I'm not sure that
it's possible to get assignments while in START state that are
significant (I'm still trying to digest SnapBuildFindSnapshot).
I would propose the attached. Andres, do you have an opinion on this?
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Andres Freund||2019-07-26 23:48:35||Re: TopoSort() fix|
|Previous Message||Alvaro Herrera||2019-07-26 22:16:56||Re: Attached partition not considering altered column properties of root partition.|