Re: PATCH: Configurable file mode mask

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>, Tom Lane <tgl@sss.pgh.pa.us>, Stephen Frost <sfrost@snowman.net>, Pg Hackers <pgsql-hackers@postgresql.org>, Adam Brightwell <adam.brightwell@crunchydata.com>
Date: 2018-01-24T03:48:07Z
Lists: pgsql-hackers
On 1/23/18 9:22 PM, Michael Paquier wrote:
> On Tue, Jan 23, 2018 at 09:18:51AM -0500, David Steele wrote:
>> On 1/20/18 5:47 PM, Michael Paquier wrote:
>>> Making this possible would require first some
>>> refactoring of PostgresNode.pm so as a node is aware of the binary paths
>>> it uses to be able to manipulate multiple instances with different
>>> install paths at the same time.
>>
>> Any idea of what the LOE would be for that?
> 
> What does LOE means?

Sorry - it means "level of effort".  I was trying to get an idea if it
is something that could be available in the PG11 development cycle, or
if I should be looking at other ways to get the testing for this patch
completed.

-- 
-David
david@pgmasters.net

Commits

  1. Allow group access on PGDATA

  2. Refactor dir/file permissions

  3. Revert "Add basic TAP test setup for pg_upgrade"

  4. Add basic TAP test setup for pg_upgrade