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
In response to Re: Assertion failure when streaming logical changes  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Assertion failure when streaming logical changes
List pgsql-hackers


On Tue, Feb 10, 2015 at 9:46 PM, Andres Freund <andres@2ndquadrant.com> wrote:
Yea, it really looks like the above commit is to "blame". The new xmin
tracking infrastructure doesn't know about the historical snapshot...

I think that we need a better regression coverage here... For example, we could add some tap tests in test_decoding to test streaming of logical changes. This would help in the future to detect such problems via the buildfarm.
--
Michael

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