Re: Assertion failure when streaming logical changes

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Assertion failure when streaming logical changes
Дата
Msg-id 20150210134322.GF21017@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Assertion failure when streaming logical changes  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Assertion failure when streaming logical changes  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
On 2015-02-10 22:06:34 +0900, Michael Paquier wrote:
> 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.

I agree. It's more or less a accident that the assert - which just
should be moved in the regd_count == 0 branch - didn't trigger for the
SQL interface. The snapshot acquired by the SELECT statement prevents it
there.

It's not entirely trivial to add tests for receivelogical though. You
need to stop it programatically after a while.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: For cursors, there is FETCH and MOVE, why no TELL?