Re: Assertion failure when streaming logical changes - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Assertion failure when streaming logical changes
Date
Msg-id CAB7nPqSKyy61HaZMa9j3FxqtD9xSuUJfa_nqciTdCuBaeyW2uA@mail.gmail.com
Whole thread Raw
In response to Re: Assertion failure when streaming logical changes  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Assertion failure when streaming logical changes  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, Feb 10, 2015 at 9:46 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">Yea,
itreally looks like the above commit is to "blame". The new xmin<br /> tracking infrastructure doesn't know about the
historicalsnapshot...<span class="HOEnZb"><font color="#888888"><br /></font></span></blockquote></div><br /></div><div
class="gmail_extra">Ithink that we need a better regression coverage here... For example, we could add some tap tests
intest_decoding to test streaming of logical changes. This would help in the future to detect such problems via the
buildfarm.<br/>-- <br /><div class="gmail_signature">Michael<br /></div></div></div> 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Assertion failure when streaming logical changes
Next
From: Michael Paquier
Date:
Subject: Re: Table-level log_autovacuum_min_duration