From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: Add const qualifiers to XLogRegister*() functions |
Date: | 2024-08-28 10:04:38 |
Message-ID: | CAJ7c6TN_dR=Js41SY98cTrifvWu_JY5++8yCez9DZ+B+2Nz06g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> On 04.10.23 16:37, Peter Eisentraut wrote:
> > On 03.10.23 13:28, Aleksander Alekseev wrote:
> >> While examining the code for similar places I noticed that the
> >> following functions can also be const'ified:
>
> >> - XLogRegisterData (?)
> >
> > I don't think this would work, at least without further work elsewhere,
> > because the data is stored in XLogRecData, which has no const handling.
>
> I got around to fixing this. Here is a patch. It allows removing a few
> unconstify() calls, which is nice.
LGTM.
Note that this may affect third-party code. IMO this is not a big deal
in this particular case.
Also by randomly checking one of the affected non-static functions I
found a bunch of calls like this:
XLogRegisterData((char *) msgs, ...)
... where the first argument is going to become (const char *). It
looks like the compilers are OK with implicitly casting (char*) to a
more restrictive (const char*) though.
--
Best regards,
Aleksander Alekseev
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2024-08-28 10:18:46 | Re: SQL Property Graph Queries (SQL/PGQ) |
Previous Message | Karina Litskevich | 2024-08-28 10:00:33 | Re: Invalid "trailing junk" error message when non-English letters are used |