Re: Some compiling warnings

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Some compiling warnings
Date: 2023-01-04 23:57:40
Message-ID: CAApHDvpfCWTqHK_xsCobejzCpS_2M_Tno8-zv4h0Ze3Tc4vr8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 4 Jan 2023 at 20:11, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>
> When trying Valgrind I came across some compiling warnings with
> USE_VALGRIND defined and --enable-cassert not configured. This is
> mainly because in this case we have MEMORY_CONTEXT_CHECKING defined
> while USE_ASSERT_CHECKING not defined.

> Attach a trivial patch for the fix.

I've just pushed that. Thanks.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-01-05 00:21:54 Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?
Previous Message Justin Pryzby 2023-01-04 23:44:24 Re: CI and test improvements