Re: pg13: xlogreader API adjust

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: pg13: xlogreader API adjust
Дата
Msg-id 20200515232428.GA31633@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: pg13: xlogreader API adjust  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: pg13: xlogreader API adjust  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-hackers
On 2020-May-15, Michael Paquier wrote:

> On Thu, May 14, 2020 at 02:12:25PM +0900, Kyotaro Horiguchi wrote:
> > Good catch!  That's not only for CreateDecodingContet. That happens
> > everywhere in the query loop in PostgresMain() until logreader is
> > initialized.  So that also happens, for example, by starting logical
> > replication using invalidated slot. Checking xlogreader != NULL in
> > WalSndErrorCleanup is sufficient.  It doesn't make actual difference,
> > but the attached explicitly initialize the pointer with NULL.
> 
> Alvaro, are you planning to look at that?  Should we have an open item
> for this matter?

On it now.  I'm trying to add a test for this (needs a small change to
PostgresNode->psql), but I'm probably doing something stupid in the Perl
side, because it doesn't detect things as well as I'd like.  Still
trying, but I may be asked to evict the office soon ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: pg_stat_wal_receiver and flushedUpto/writtenUpto
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_stat_wal_receiver and flushedUpto/writtenUpto