Re: pgsql: Fix memory leak in pgbench

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Fix memory leak in pgbench
Date: 2019-04-12 06:57:41
Message-ID: alpine.DEB.2.21.1904120833110.8912@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers


Hello Tom,

>> I can add it in the compiler version, something like:
>> "Ubuntu 18.04.2 LTS **EXPERIMENTAL** gcc ..."
>
> +1.

Done, should be seen on next run.

The list of compilers is accumulating on the "Members" page for caiman,
handfish, moonjelly and seawasp. Not sure how useful it is to keep an
extended history for quickly moving targets.

I'd be interested in running corresponding -Werror animals, which would be
likely to be in the red, if it would be acceptable with some
**EXPERIMENTAL** or even **IGNORE** warning. Hmmm, probably people like to
see an all green status page.

> Also you might consider marking that in a "note" for the animal.

I have, but have not found where to put an animal note.

--
Fabien.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2019-04-12 12:13:29 pgsql: Show shared object statistics in pg_stat_database
Previous Message Peter Eisentraut 2019-04-12 06:43:11 pgsql: Fix REINDEX CONCURRENTLY of partitions