| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Jammie <shailesh(dot)jamloki(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Movement of restart_lsn position movement of logical replication slots is very slow |
| Date: | 2020-12-24 14:15:23 |
| Message-ID: | CAA4eK1KMvTD=u3XRb88-=XuzvcYWkkmwj_vQ1C+LkpRxGGnFkg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 24, 2020 at 7:30 PM Jammie <shailesh(dot)jamloki(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-12-24 14:30:09 | Re: postgres_fdw - cached connection leaks if the associated user mapping/foreign server is dropped |
| Previous Message | Fujii Masao | 2020-12-24 14:13:29 | Re: postgres_fdw - cached connection leaks if the associated user mapping/foreign server is dropped |