Horton

Re: buildfarm warnings

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org, Robert Haas <rhaas@postgresql.org>, Alexander Korotkov <akorotkov@postgresql.org>
Date: 2022-02-12T22:03:03Z
Lists: pgsql-hackers 
Hi,

On 2022-02-12 16:42:03 -0500, Tom Lane wrote:
> Another new one that maybe should be silenced is
>
> /mnt/resource/bf/build/skink-master/HEAD/pgsql.build/../pgsql/src/backend/access/heap/vacuumlazy.c:1129:41: warning: 'freespace' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> Only skink and frogfish are showing that, though.

skink uses -O1 to reduce the overhead of valgrind a bit (iirc that shaved off
a couple of hours) without making backtraces completely unreadable. Which
explains why it shows different warnings than most other animals...

Greetings,

Andres Freund

Commits

  1. Avoid dangling-pointer usage in pg_basebackup progress reports.

  2. Delete contrib/xml2's legacy implementation of xml_is_well_formed().