From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Make pgoutput documentation easier to find |
Date: | 2025-08-14 16:10:58 |
Message-ID: | CAHGQGwFE66PC72WU856_KH-VSrmSs3U4Pv0PL32KR5C_fRUvfw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Thu, Aug 14, 2025 at 9:12 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> Since pgoutput can only generate the binary output, it pg_logical_slot_get_changes()
> cannot be used with this plugin. I felt this should be also documented.
OK, I added this note in the 0002 patch attached earlier.
> Another point: test_decoding does not have descriptions for their options neither.
> Should we also add as well?
Yes, I think it's worth doing this (but it's better to do as a separate patch).
TBH this was already on my TODO list.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Benoît Dufour | 2025-08-14 16:14:17 | Re: [Feature request] Add a way to get the length of a PQerrorMessage in libpq |
Previous Message | Fujii Masao | 2025-08-14 16:05:48 | Re: Make pgoutput documentation easier to find |
From | Date | Subject | |
---|---|---|---|
Previous Message | Fujii Masao | 2025-08-14 16:05:48 | Re: Make pgoutput documentation easier to find |