| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GCC 7 warnings |
| Date: | 2017-05-04 04:21:38 |
| Message-ID: | 19105.1493871698@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 4/10/17 11:03, Peter Eisentraut wrote:
>> The release of GCC 7 is approaching [0], and the number of warnings in
>> PostgreSQL has gone up since we last looked [1]. Output attached. (My
>> version is 7.0.1 20170408.)
> GCC 7 has been released.
> Should we backpatch these warning fixes? The commit in question is
> 6275f5d28a1577563f53f2171689d4f890a46881. (I haven't actually checked
> whether backpatches well.)
Seems like that patch represents generally better coding practice,
and applying it would reduce cross-branch differences that would be
hazards for future patches, so I'm mostly +1 for this.
But I'd suggest waiting till after next week's releases. If there
are any problems induced by this, we'd be more likely to find them
with another three months' time before it hits the wild.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-05-04 04:50:16 | Re: PROVE_FLAGS |
| Previous Message | Stephen Frost | 2017-05-04 04:19:04 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |