Re: Fixing warnings in back branches? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fixing warnings in back branches?
Date
Msg-id CA+TgmoYbHb=ZDtM26g211vqtD2G3VcY0VOmPiFw-DLO6AA4RbQ@mail.gmail.com
Whole thread Raw
In response to Re: Fixing warnings in back branches?  (Andres Freund <andres@anarazel.de>)
Responses Re: Fixing warnings in back branches?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Dec 15, 2015 at 7:59 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-12-14 11:00:32 -0500, Robert Haas wrote:
>> On Mon, Dec 14, 2015 at 10:06 AM, Andres Freund <andres@anarazel.de> wrote:
>> > to compile 9.1 without warnings. -Wincompatible-pointer-types is quite
>> > useful to detect problems. The rest indeed is pretty 'Meh'.
>>
>> IIUC, the main thing that causes incompatible pointer type warnings on
>> 9.1 is the conflation of FILE with gzFile in pg_dump and
>> pg_basebackup.
>
> Right.
>
>> Not sure exactly which commits fixed that offhand.
>
> d923125b77c5d698bb8107a533a21627582baa43 , but that doesn't fix the
> 'files' output format, which was removed in
> 19f45565f581ce605956c29586bfd277f6012eec

Well, we're not going to back-patch the removal of the files format, right?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Fixing warnings in back branches?
Next
From: Andres Freund
Date:
Subject: Re: Fixing warnings in back branches?