Re: logical changeset generation v3 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: logical changeset generation v3
Date
Msg-id CAB7nPqRTqdeHiX+X6bBZK6d=A2vUCSX71ikKjhr94_XiyXRmQA@mail.gmail.com
Whole thread Raw
In response to Re: logical changeset generation v3  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: logical changeset generation v3  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
<br /><br /><div class="gmail_quote">On Wed, Nov 21, 2012 at 4:34 PM, Andres Freund <span dir="ltr"><<a
href="mailto:andres@2ndquadrant.com"target="_blank">andres@2ndquadrant.com</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="h5">On 2012-11-21
14:57:08+0900, Michael Paquier wrote:<br /><br /></div>Ah, I see. Could you try the following diff?<br /><br /> diff
--gita/src/backend/replication/logical/snapbuild.c<br /> b/src/backend/replication/logical/snapbuild.c<br /> index
df24b33..797a126100644<br /> --- a/src/backend/replication/logical/snapbuild.c<br /> +++
b/src/backend/replication/logical/snapbuild.c<br/> @@ -471,6 +471,7 @@ SnapBuildDecodeCallback(ReorderBuffer
*reorder,<br/> Snapstate *snapstate,<br />                  */<br />                 snapstate->transactions_after =
buf->origptr;<br/><br /> +               snapstate->nrrunning = running->xcnt;<br />                
snapstate->xmin_running= InvalidTransactionId;<br />                 snapstate->xmax_running =
InvalidTransactionId;<br/></blockquote></div>I am still getting the same assertion failure even with this diff
included.<br/>-- <br />Michael Paquier<br /><a href="http://michael.otacoo.com"
target="_blank">http://michael.otacoo.com</a><br/> 

pgsql-hackers by date:

Previous
From: Shigeru Hanada
Date:
Subject: Re: FDW for PostgreSQL
Next
From: Kohei KaiGai
Date:
Subject: Re: FDW for PostgreSQL