From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | is pg_log_standby_snapshot() really needed? |
Date: | 2023-06-07 05:32:22 |
Message-ID: | CAJKUy5jnoEkyuWnxcfoq+2A91G9_9u=wdOUfoFg3koxA5ckLig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I'm testing the ability to have a logical replica subscribed from a standby.
Of course, I'm doing this in a laboratory with no activity so
everything get stuck after creating the subscription (the main slot).
This is clearly because every time it will create a temp slot for copy
a table it needs the running xacts from the primary.
Now, I was solving this by executing CHECKPOINT on the primary, and
also noted that pg_switch_wal() works too. After that, I read about
pg_log_standby_snapshot().
So, I wonder if that function is really needed because as I said I
solved it with already existing functionality. Or if it is really
needed maybe it is a bug that a CHECKPOINT and pg_switch_wal() have
the same effect?
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-06-07 05:53:35 | Re: Reload configuration more frequently in apply worker. |
Previous Message | Amit Kapila | 2023-06-07 05:18:50 | Re: TRAP: FailedAssertion("prev_first_lsn < cur_txn->first_lsn", File: "reorderbuffer.c", Line: 927, PID: 568639) |