is pg_log_standby_snapshot() really needed? - Mailing list pgsql-hackers

From Jaime Casanova
Subject is pg_log_standby_snapshot() really needed?
Date
Msg-id CAJKUy5jnoEkyuWnxcfoq+2A91G9_9u=wdOUfoFg3koxA5ckLig@mail.gmail.com
Whole thread Raw
Responses Re: is pg_log_standby_snapshot() really needed?
List 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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: TRAP: FailedAssertion("prev_first_lsn < cur_txn->first_lsn", File: "reorderbuffer.c", Line: 927, PID: 568639)
Next
From: Amit Kapila
Date:
Subject: Re: Reload configuration more frequently in apply worker.