Re: Improve doc on parallel stream changes for Stream Abort message

From: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve doc on parallel stream changes for Stream Abort message
Date: 2025-06-24 06:28:17
Message-ID: CAO6_XqrnZiu7qO8EETuG+etkUBr=Ju4d8A6SOPGN_WpQcFxNMQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 24, 2025 at 7:26 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sutou Kouhei 2025-06-24 07:10:09 Re: Make COPY format extendable: Extract COPY TO format implementations
Previous Message Masahiko Sawada 2025-06-24 06:24:23 Re: Make COPY format extendable: Extract COPY TO format implementations