Re: Movement of restart_lsn position movement of logical replication slots is very slow

Поиск
Список
Период
Сортировка
От Jammie
Тема Re: Movement of restart_lsn position movement of logical replication slots is very slow
Дата
Msg-id CAFt1pcqRv3-u4FcSZ8a+1OvzXfiwy3wop7Wt2Xf0U0o17RWvMQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Movement of restart_lsn position movement of logical replication slots is very slow  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: Movement of restart_lsn position movement of logical replication slots is very slow  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
Hi Amit, 
Thanks for the response .
Can you please let me know what pg_current_wal_lsn returns ?

is this position the LSN of the next log record to be created, or is it the LSN of the last log record already created and inserted in the log?

The document says 
- it returns current WAL write location.

Regards
Shailesh

On Thu, 24 Dec, 2020, 7:43 pm Amit Kapila, <amit.kapila16@gmail.com> wrote:
On Thu, Dec 24, 2020 at 7:30 PM Jammie <shailesh.jamloki@gmail.com> wrote:
>
> Sorry dont have the debug setup handy. However the sql commands now works though to move the restart_lsn of the slots in standlone code from psql.
>
>  A few followup questions.
>
> What is catalog_xmin in the pg_replication_slots ? and how is it playing role in moving the restart_lsn of the slot.
>
> I am just checking possibility that if a special transaction can cause private slot to stale ?
>

Yeah, it is possible if there is some old transaction is active in the
system. The restart_lsn is lsn required by the oldesttxn. But it is
strange that it affects only one of the slots.

--
With Regards,
Amit Kapila.

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

Предыдущее
От: Neil Chen
Дата:
Сообщение: Re: Key management with tests
Следующее
От: "Andrey V. Lepikhov"
Дата:
Сообщение: Re: [POC] Fast COPY FROM command for the table with foreign partitions