On Thu, Aug 14, 2025 at 9:12 PM Hayato Kuroda (Fujitsu)
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
Dear Fujii-san,
> The current documentation for pgoutput is buried in the logical streaming
> replication protocol section (in protocol.sgml), and there's no index entry
> for it. This makes it hard to discover and access, for example, when trying
> to look up the options it supports.
>
> I've oft
On Thu, Aug 7, 2025 at 10:35 PM Euler Taveira 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 de
On Wed, Aug 6, 2025, at 10:48 AM, Fujii Masao wrote:
> On Wed, Aug 6, 2025 at 8:36 PM Peter Eisentraut wrote:
>>
>> On 03.08.25 03:32, Fujii Masao wrote:
>> > The current documentation for pgoutput is buried in the logical streaming
>> > replication protocol section (in protocol.sgml), and there's
On Wed, Aug 6, 2025 at 8:36 PM Peter Eisentraut wrote:
>
> On 03.08.25 03:32, Fujii Masao wrote:
> > The current documentation for pgoutput is buried in the logical streaming
> > replication protocol section (in protocol.sgml), and there's no index entry
> > for it. This makes it hard to discover
On 03.08.25 03:32, Fujii Masao wrote:
The current documentation for pgoutput is buried in the logical streaming
replication protocol section (in protocol.sgml), and there's no index entry
for it. This makes it hard to discover and access, for example, when trying
to look up the options it support
