On Tue, 10 Oct 2023 at 06:59, Kyotaro Horiguchi wrote:
>
> At Fri, 6 Oct 2023 14:58:13 +0530, vignesh C wrote in
> > On Fri, 30 Apr 2021 at 11:53, Dilip Kumar wrote:
> > > It makes sense to include xid in the debug message, earlier I thought
> > > that will it be a good idea to also print the
At Fri, 6 Oct 2023 14:58:13 +0530, vignesh C wrote in
> On Fri, 30 Apr 2021 at 11:53, Dilip Kumar wrote:
> > It makes sense to include xid in the debug message, earlier I thought
> > that will it be a good idea to also print the toplevel_xid. But I
> > think it is for debug purposes and only
On Fri, 30 Apr 2021 at 11:53, Dilip Kumar wrote:
>
> On Thu, Apr 29, 2021 at 9:45 PM vignesh C wrote:
> >
> > Hi,
> >
> > While debugging one of the logical decoding issues, I found that xid was
> > not included in restoring reorder buffer changes from disk log messages.
> > Attached a patch
On Thu, Apr 29, 2021 at 9:45 PM vignesh C wrote:
>
> Hi,
>
> While debugging one of the logical decoding issues, I found that xid was not
> included in restoring reorder buffer changes from disk log messages.
> Attached a patch for it. I felt including the XID will be helpful in
> debugging.
Hi,
While debugging one of the logical decoding issues, I found that xid was
not included in restoring reorder buffer changes from disk log messages.
Attached a patch for it. I felt including the XID will be helpful in
debugging. Thoughts?
Regards,
Vignesh
From
