Re: pgsql: Allow group access on PGDATA

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Allow group access on PGDATA
Date: 2018-04-07 22:08:57
Message-ID: CAH2-Wz=LvbiwHGoHfSx4ox53zd7+W09Pq7MLFPcGumciXUX+Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Apr 7, 2018 at 2:46 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Allow group access on PGDATA
>
> Allow the cluster to be optionally init'd with read access for the
> group.

Looks like this broke prion and culicidae. On culicidae, clearly the
problem is here:

"""
Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
./analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
./delete_old_cluster.sh
+ find /home/andres/build/buildfarm-culicidae/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/data
-type f ! -perm 640
+ wc -l
+ [ 1778 -ne 0 ]
+ echo files in PGDATA with permission != 640
files in PGDATA with permission != 640
+ exit 1
+ rm -rf /tmp/pg_upgrade_check-h6epmk
make: *** [Makefile:40: check] Error 1
"""

--
Peter Geoghegan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-04-07 22:12:36 Re: pgsql: Allow group access on PGDATA
Previous Message Tom Lane 2018-04-07 21:57:30 Re: pgsql: Support partition pruning at execution time