On Sat, Dec 24, 2016 at 7:48 AM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Andrew Dunstan wrote: > >> ... and miraculously it has fixed itself. > > And it failed again today, once. > > Today I noticed that it's running gcc 4.5.0. But for the 4.5 branch, > the GCC guys put out a few releases before abandoning it, and there are > some compiler segmentation faults fixed in some of these releases, > visible here: > > https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.1 > https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.2 > https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.3 > https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.4 > > I think it'd be worthwhile to upgrade to the latest in that branch.
FWIW, I also saw segmentation faults with MinGW using gcc 4.8.1 in my environments, after fetching the newest supported by the builds :( Any configuration on Windows out of MSVC is depressing. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
