Re: Make pgoutput documentation easier to find

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Euler Taveira <euler(at)eulerto(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Make pgoutput documentation easier to find
Date: 2025-08-08 15:26:02
Message-ID: CAHGQGwG0zPyz0BqY5sR2y4OpTWQu9Sb2POH76wzG8_K-AJ72dQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, Aug 7, 2025 at 10:35 PM Euler Taveira <euler(at)eulerto(dot)com> wrote:
> Since you are proposing this change, I'm wondering if we shouldn't move
> "Writing Logical Decoding Output Plugins" to "Internals" chapter. It contains
> information to PostgreSQL developers.

Maybe, but I don’t have a strong opinion. If we decide to do it, it would
be better to make the change in a separate patch.

Regards,

--
Fujii Masao

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2025-08-09 15:27:17 Wrong Installation Link
Previous Message PG Doc comments form 2025-08-08 05:14:56 Removing publicly-writable schemas from search_path with ECPG