Re: [PATCH] Remove workarounds to format [u]int64's

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [PATCH] Remove workarounds to format [u]int64's
Date: 2022-03-21 09:12:33
Message-ID: CALT9ZEH1HHYgU6QKzX9qwuGcYpqr5Nojgphu9zG3fYXxTtmiTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

пн, 21 мар. 2022 г. в 12:52, Aleksander Alekseev <aleksander(at)timescale(dot)com>:

> Hi hackers,
>
> I learned from Tom [1] that we can simplify the code like:
>
> ```
> char buff[32];
> snprintf(buf, sizeof(buf), INT64_FORMAT, ...)
> ereport(WARNING, (errmsg("%s ...", buf)));
> ```
>
> ... and rely on %lld/%llu now as long as we explicitly cast the
> argument to long long int / unsigned long long. This was previously
> addressed in 6a1cd8b9 and d914eb34, but I see more places where we
> still use an old approach.
>
> Suggested patch fixes this. Tested locally - no warnings; passes all the
> tests.
>
> [1]
> https://www.postgresql.org/message-id/771048.1647528068%40sss.pgh.pa.us
>
> Hi, Alexander!
Probably you can do (long long) instead of (long long int). It is shorter
and this is used elsewhere in the code.

--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com <http://www.postgrespro.com>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2022-03-21 09:23:33 Re: [PATCH] Remove workarounds to format [u]int64's
Previous Message Aleksander Alekseev 2022-03-21 08:52:14 [PATCH] Remove workarounds to format [u]int64's