Re: Synchronizing slots from primary to standby

Поиск
Список
Период
Сортировка
От shveta malik
Тема Re: Synchronizing slots from primary to standby
Дата
Msg-id CAJpy0uBd79AD+qm-ps9nqfrqmy7qrcyGGsCs1u3FHQO-S3cS5g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Synchronizing slots from primary to standby  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Ответы Re: Synchronizing slots from primary to standby  (shveta malik <shveta.malik@gmail.com>)
Re: Synchronizing slots from primary to standby  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Список pgsql-hackers
On Thu, Feb 22, 2024 at 4:35 PM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
>
> Suppose that in synchronize_slots() the query would be:
>
>     const char *query = "SELECT slot_name, plugin, confirmed_flush_lsn,"
>         " restart_lsn, catalog_xmin, two_phase, failover,"
>         " database, conflict_reason"
>         " FROM pg_catalog.pg_replication_slots"
>         " WHERE failover and NOT temporary and 1 = 1";
>
> Then my comment is to rewrite it to:
>
>     const char *query = "SELECT slot_name, plugin, confirmed_flush_lsn,"
>         " restart_lsn, catalog_xmin, two_phase, failover,"
>         " database, conflict_reason"
>         " FROM pg_catalog.pg_replication_slots"
>         " WHERE failover and NOT temporary and 1 OPERATOR(pg_catalog.=) 1";
>
> to ensure the operator "=" is coming from the pg_catalog schema.
>

Thanks for the details, but slot-sync does not use SPI calls, it uses
libpqrcv calls. So is this change needed?

thanks
Shveta



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

Предыдущее
От: "Euler Taveira"
Дата:
Сообщение: Re: speed up a logical replica setup
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Slow catchup of 2PC (twophase) transactions on replica in LR