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

From Robert Haas
Subject Re: Fixing warnings in back branches?
Date
Msg-id CA+TgmoYoQQeyR3kXG0v8Yg+STmT3ef0Mwcd-UteKMUSz83huRQ@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 8:17 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-12-15 08:13:06 -0500, Robert Haas wrote:
>> 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:
>> >> 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?
>
> Obviously not.

So... that means we can't really get rid of these warnings on 9.1,
IIUC.  I agree it would be nice to do if this were no issue, but as it
is I'm inclined to think we should just live with it for the next ~10
months.  After that 9.1 will no longer be a supported branch.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: 9.5RC1 wraps *today*
Next
From: Tom Lane
Date:
Subject: Re: small query, about skipping dump in dumpAttrDef