From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: AlterSubscription_refresh "wrconn" wrong variable? |
Date: | 2021-05-06 21:08:50 |
Message-ID: | 4181370.1620335330@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2021-May-06, Peter Smith wrote:
>> PSA v3 of the patch. Same as before, but now also renames the global
>> variable from "wrconn" to "lrep_worker_wrconn".
> I think there are two patches here -- the changes to
> AlterSubscription_refresh are a backpatchable bugfix, and the rest of it
> can just be applied to master.
The rename of that variable is just cosmetic, true, but I'd still be
inclined to back-patch it. If we don't do so then I'm afraid that
future back-patched fixes might be bitten by the same confusion,
possibly introducing new real bugs.
Having said that, keeping the two aspects in separate patches might
ease review and testing.
> In my mind we make a bit of a distinction for global variables by using
> CamelCase rather than undercore_separated_words.
I think it's about 50/50, TBH. I'd stick with whichever style is
being used in nearby code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2021-05-06 21:11:31 | Re: alter table set TABLE ACCESS METHOD |
Previous Message | Alvaro Herrera | 2021-05-06 20:58:28 | Re: AlterSubscription_refresh "wrconn" wrong variable? |