Date: Fri, 19 May 2023 08:29:06 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 16 draft release notes ready
Message-ID: <ZGdrko+a/QpwQdSg@momjian.us>
References: <ZGaPa7M3gc2THeDJ@momjian.us>
 <890b2035-7bd0-c243-de7c-84809b35ffb0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <890b2035-7bd0-c243-de7c-84809b35ffb0@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/ZGdrko%2Ba/QpwQdSg%40momjian.us>
Precedence: bulk

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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.