From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Included xid in restoring reorder buffer changes from disk log message |
Date: | 2023-10-06 09:28:13 |
Message-ID: | CALDaNm3-MTwMkeuWfVr22_B123M8D9PNn8TwCwmp40BFarAw7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 30 Apr 2021 at 11:53, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Thu, Apr 29, 2021 at 9:45 PM vignesh C <vignesh21(at)gmail(dot)com> 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. Thoughts?
> >
>
> 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 we have the xid we can fetch
> the other parameters so maybe adding xid is good enough.
While having a look at the reorderbuffer code, I noticed that this
changes were still not committed.
Here is a rebased version of the patch.
Regards,
Vignesh
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Include-xid-in-restoring-reorder-buffer-changes-f.patch | text/x-patch | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2023-10-06 10:00:33 | typo in couple of places |
Previous Message | Amit Langote | 2023-10-06 09:23:37 | Re: remaining sql/json patches |