Re: BUG #19868: pg_resetwal prints uint32 WAL segment size as -1 bytes

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: 1548140642(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19868: pg_resetwal prints uint32 WAL segment size as -1 bytes
Date: 2026-11-11 13:12:06
Message-ID: b706f417-b7c2-47f1-9b8c-80ff3953aa4e@iki.fi
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11/11/2026 07:48, PG Bug reporting form wrote:
> When pg_resetwal -n reads a damaged pg_control whose uint32 xlog_seg_size
> field contains 4294967295, its invalid-WAL-segment-size warning prints "-1
> bytes". The diagnostic should preserve the unsigned field value and print
> "4294967295 bytes".

This is completely inconsequential.

Peter Eisentraut experimented with -Wformat=signedness a while back, see
https://www.postgresql.org/message-id/a37346d0-96d0-42f1-a5d9-8f31872818c6@eisentraut.org.
This particular change was also covered by those patches.

- Heikki

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2026-11-11 13:15:20 Re: BUG #19867: pg_verifybackup accepts out-of-range Timeline in backup manifest
Previous Message PG Bug reporting form 2026-11-11 13:09:08 BUG #19878: pg_identify_object functions expose XX000 for unsupported class IDs