Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <hornschnorter@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Hao Lee <mixtrue@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2018-05-15T16:54:05Z
Lists: pgsql-hackers
Mark Dilger <hornschnorter@gmail.com> writes: > I'm curious why the Windows build farm members did not pick this up. Or > perhaps they did? (I don't get emails about that.) They did not, and I too was wondering why not. > If none of the animals > are configured to detect this bug, perhaps the community needs another > Windows animal configured along the lines of the build machine I am using? +1. How do you have yours configured, anyway? regards, tom lane
Commits
-
Fix for globals.c- c.h must come first
- e2b83ff556de 11.0 landed
-
Allow group access on PGDATA
- c37b3d08ca68 11.0 cited
-
Refactor dir/file permissions
- da9b580d8990 11.0 cited