Re: pgsql: Fix memory leak in pgbench

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, 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-11 02:16:18
Message-ID: CA+hUKGKfZKKHOEFvUBi1RjjhN4kTZSbY4qiMxi0GbOK=0WDHHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Apr 10, 2019 at 11:12 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Apr 10, 2019 at 04:05:34PM +0900, Masahiko Sawada wrote:
> > Thank you! I didn't know the detail of that PostgreSQL supports C99
> > standard but I hope the warning will be fixed and coming patches will
> > still obey that rule.
>
> Ah, thanks I missed that bit from the docs. I should have paid more
> attention. I am sure that Álvaro will address your patch in a timely
> manner.

. o O ( Is it time to run with -Werror on some BF animals yet? )

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-04-11 03:57:12 pgsql: Fix declaration after statement
Previous Message Tom Lane 2019-04-10 23:04:50 pgsql: Fix backwards test in operator_precedence_warning logic.