Re: pgsql: Allow group access on PGDATA
От | Peter Geoghegan |
---|---|
Тема | Re: pgsql: Allow group access on PGDATA |
Дата | |
Msg-id | CAH2-Wz=LvbiwHGoHfSx4ox53zd7+W09Pq7MLFPcGumciXUX+Wg@mail.gmail.com обсуждение исходный текст |
Ответ на | pgsql: Allow group access on PGDATA (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: pgsql: Allow group access on PGDATA
Re: pgsql: Allow group access on PGDATA |
Список | pgsql-committers |
On Sat, Apr 7, 2018 at 2:46 PM, Stephen Frost <sfrost@snowman.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
В списке pgsql-committers по дате отправления: