Re: Improve doc on parallel stream changes for Stream Abort message - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Improve doc on parallel stream changes for Stream Abort message
Date
Msg-id CAA4eK1L=ZJNqWd-VcTGrfAm3_+3OsrVULDuWOQ4gWNK-+Ls9tg@mail.gmail.com
Whole thread Raw
In response to Re: Improve doc on parallel stream changes for Stream Abort message  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
List pgsql-hackers
On Tue, Jun 24, 2025 at 11:58 AM Anthonin Bonnefoy
<anthonin.bonnefoy@datadoghq.com> wrote:
>
> On Tue, Jun 24, 2025 at 7:26 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > How about a slightly modified version like: (a) The LSN of the abort
> > operation, present only when the change stream can be applied in
> > parallel. This field is available since protocol version 4. (b) Abort
> > timestamp of the transaction, present only when the change stream can
> > be applied in parallel. The value is in number of microseconds since
> > PostgreSQL epoch (2000-01-01). This field is available since protocol
> > version 4.
>
> What about ", present only when streaming is set to parallel"? I think
> clarifying the relation between streaming=parallel and the presence of
> those fields is the important part.
>

Works for me. I'll wait till tomorrow morning to see if there are any
further comments, and then push it.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: Bertrand Drouvot
Date:
Subject: Re: pgsql: Introduce pg_shmem_allocations_numa view