From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 16 draft release notes ready |
Date: | 2023-05-19 12:29:06 |
Message-ID: | ZGdrko+a/QpwQdSg@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 19, 2023 at 09:49:18AM +0200, Drouvot, Bertrand wrote:
> Thanks!
>
> "
> This adds the function pg_log_standby_snapshot(). TEXT?:
> "
>
> My proposal:
>
> This adds the function pg_log_standby_snapshot() to log details of the current snapshot
> to WAL. If the primary is idle, the slot creation on a standby can take a while.
> This function can be used on the primary to speed up the logical slot creation on
> the standby.
Yes, I got this concept from the commit message, but I am unclear on
what is actually happening so I can clearly explain it. Slot creation
on the standby needs a snapshot, and that is only created when there is
activity, or happens periodically, and this forces it to happen, or
something? And what snapshot is this? The current session's?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2023-05-19 12:53:45 | Re: The documentation for READ COMMITTED may be incomplete or wrong |
Previous Message | Bruce Momjian | 2023-05-19 12:09:54 | Naming of gss_accept_deleg |