Re: doc patch: correct function name for slot synchronization.

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: doc patch: correct function name for slot synchronization.
Date: 2025-08-21 09:13:05
Message-ID: CAA4eK1JJzXMztyfH0uj3DYMzmjAui3UPUUpAtU+o=74yKyW0_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 21, 2025 at 2:24 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear hackers,
> (CC: Amit and Shveta, who were the committer and author)
>
> While working on the translation project of manuals, I found below sentence:
>
> >
> When slot synchronization is configured as recommended, and the initial
> synchronization is performed either automatically or manually via
> pg_sync_replication_slot, ...
> >
>
> However, the correct function name is pg_sync_replication_slots, and it should
> be tagged as a function. Please see attached to address the issue. The typo exists
> till PG17.
>

Thanks for noticing this and providing a patch. I'll take care of this.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-08-21 09:55:29 Re: memory leak in logical WAL sender with pgoutput's cachectx
Previous Message Shubham Khanna 2025-08-21 09:08:33 Re: Add support for specifying tables in pg_createsubscriber.