From: | Amul Sul <sulamul(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Correct comment in StartupXLOG(). |
Date: | 2021-02-03 11:06:13 |
Message-ID: | CAAJ_b94viPF5y7wvpP6Hccpy0Q3cnvQt77ibM=fCcUPFSygzzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 3, 2021 at 2:48 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Wed, Feb 3, 2021 at 2:28 PM Amul Sul <sulamul(at)gmail(dot)com> wrote:
> >
> > Hi,
> >
> > SharedRecoveryState member of XLogCtl is no longer a boolean flag, got changes
> > in 4e87c4836ab9 to enum but, comment referring to it still referred as the
> > boolean flag which is pretty confusing and incorrect.
>
> +1 for the comment change
>
> > Also, the last part of the same comment is as:
> >
> > " .. although the boolean flag to allow WAL is probably atomic in
> > itself, .....",
> >
> > I am a bit confused here too about saying "atomic" to it, is that correct?
> > I haven't done anything about it, only replaced the "boolean flag" to "recovery
> > state" in the attached patch.
>
> I don't think the atomic is correct, it's no more boolean so it is
> better we get rid of this part of the comment
Thanks for the confirmation. Updated that part in the attached version.
Regards,
Amul
Attachment | Content-Type | Size |
---|---|---|
v2_fix_comment_in_StartupXLOG.patch | application/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-02-03 12:04:09 | Re: Dumping/restoring fails on inherited generated column |
Previous Message | Bharath Rupireddy | 2021-02-03 11:05:29 | Re: logical replication worker accesses catalogs in error context callback |