Re: PATCH: Configurable file mode mask

Michael Paquier <michael.paquier@gmail.com>

From: Michael Paquier <michael.paquier@gmail.com>
To: David Steele <david@pgmasters.net>
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-24T02:22:41Z
Lists: pgsql-hackers
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?
--
Michael

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