From: | rajesh singarapu <rajesh(dot)rs0541(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Use proc instead of MyProc in ProcArrayGroupClearXid()/TransactionGroupUpdateXidStatus() |
Date: | 2022-11-08 06:58:30 |
Message-ID: | CADgiWi6bjr=3KhmfBB7WYOGRY7wrZ4w0p-NF+3MgBGH3b8tAFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks Bharat and Amit for the review and explaining rationale.
for the TransactionGroupUpdateXidStatus() change, let me see if I can
piggy back this change on something more valuable.
thanks
Rajesh
On Tue, Nov 8, 2022 at 11:58 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Mon, Nov 7, 2022 at 3:17 PM rajesh singarapu <rajesh(dot)rs0541(at)gmail(dot)com> wrote:
> >
> > In both TransactionGroupUpdateXidStatus and ProcArrayGroupClearXid
> > global MyProc is used. for consistency, replaced with a function local variable.
> >
>
> In ProcArrayGroupClearXid(), currently, we always pass MyProc as proc,
> so the change suggested by you will work but I think if in the future
> someone calls it with a different proc, then the change suggested by
> you won't work. The change in TransactionGroupUpdateXidStatus() looks
> good but If we don't want to change ProcArrayGroupClearXid() then I am
> not sure if there is much value in making the change in
> TransactionGroupUpdateXidStatus().
>
> --
> With Regards,
> Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2022-11-08 07:17:23 | Re: Reviving lost replication slots |
Previous Message | Richard Guo | 2022-11-08 06:51:00 | Re: Add proper planner support for ORDER BY / DISTINCT aggregates |