| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GCC 7 warnings |
| Date: | 2017-05-04 01:59:21 |
| Message-ID: | b79425b4-288b-19f7-2fb6-b65fc2a772bc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.)
PG 9.2 and newer compile warning-free with GCC 6, so there would be some
value in preserving this with GCC 7.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-05-04 02:31:15 | Re: statement_timeout is not working as expected with postgres_fdw |
| Previous Message | Haribabu Kommi | 2017-05-04 00:30:44 | Re: Re: [BUGS] BUG #14634: On Windows pg_basebackup should write tar to stdout in binary mode |