Re: pgsql: Fix memory leak in pgbench - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Fix memory leak in pgbench
Date
Msg-id 8005.1554989723@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Fix memory leak in pgbench  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Fix memory leak in pgbench  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Apr 11, 2019 at 09:03:19AM +0200, Fabien COELHO wrote:
>> I can set up farm animals with bleeding age clang/gcc (compiled weekly from
>> sources) with -Werror (seawasp & moonjelly are already running with those
>> but without -Werror).

> If possible, I would not recommend using compiled versions from
> source, but just the latest stable versions released for gcc and 
> clang.  Even if this can catch up compiler bugs using Postgres code at
> a very early stage, the false positives induced have been proving to
> hurt because of the time investigations took to determine if this was
> a problem on our side or not.

Yeah, I'm not excited about having to expend effort on working around
warnings seen only in unstable compilers.  I was thinking more of
using some solid-but-not-ancient gcc release.

            regards, tom lane



pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Fix declaration after statement
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Fix memory leak in pgbench