Re: Adjust the description of OutputPluginCallbacks in pg-doc - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Adjust the description of OutputPluginCallbacks in pg-doc
Date
Msg-id CAA4eK1K6t6SQn_FDKE2xKX7S4-xT-joCvVn8bCL7YL+KhU0ygw@mail.gmail.com
Whole thread Raw
In response to Re: Adjust the description of OutputPluginCallbacks in pg-doc  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Thu, Jan 19, 2023 at 4:47 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Jan 11, 2023 at 4:20 PM wangw.fnst@fujitsu.com
> <wangw.fnst@fujitsu.com> wrote:
> >
> > When I was reading the "Logical Decoding Output Plugins" chapter in pg-doc [1],
> > I think in the summary section, only the callback message_cb is not described
> > whether it is required or optional, and the description of callback
> > stream_prepare_cb seems inaccurate.
> >
> > And after the summary section, I think only the callback stream_xxx_cb section
> > and the callback truncate_cb section are not described this tag (are they
> > required or optional).
> >
> > I think we could improve these to be more reader friendly. So I tried to write
> > a patch for these and attach it.
> >
> > Any thoughts?
> >
>
> This looks mostly good to me. I have made minor adjustments in the
> attached. Do those make sense to you?
>

I forgot to mention that I intend to commit this only on HEAD as this
is a doc improvement patch.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Next
From: vignesh C
Date:
Subject: Re: Add the ability to limit the amount of memory that can be allocated to backends.