Re: Fix unsigned output for signed values in SLRU error reporting

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>
Subject: Re: Fix unsigned output for signed values in SLRU error reporting
Date: 2022-04-06 07:31:30
Message-ID: 7764bbea-5e30-0122-02e3-4860bd9190ea@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25.03.22 11:49, Pavel Borisov wrote:
> It's true that offset can not be negative, but printing int value as %u
> isn't nice even if it is not supposed to be negative. So I'd propose the
> small patch in this thread be applied separately if none has anything
> against it.

committed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-04-06 07:38:52 Re: MERGE bug report
Previous Message Amit Langote 2022-04-06 07:20:46 Re: generic plans and "initial" pruning