| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Adam Brightwell <adam(dot)brightwell(at)crunchydata(dot)com> |
| Subject: | Re: PATCH: Configurable file mode mask |
| Date: | 2018-01-23 14:33:47 |
| Message-ID: | 1fa55178-df84-31fa-17d1-45b11ed05307@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/23/18 9:26 AM, Tom Lane wrote:
> David Steele <david(at)pgmasters(dot)net> writes:
>> Unless I read it wrong the buildfarm is not doing cross-version
>> upgrades, but a developer/user can do so manually using the same script?
>
> The buildfarm isn't doing that *by default*, but Andrew has at least
> one critter configured to do so (crake I think). It found a bug just
> a couple days ago too, so losing that capability isn't going to sell.
Thanks for the clarification, Tom.
What if I update pg_upgrade/test.sh to optionally allow group
permissions and we configure an animal to test it if it gets committed?
It's not ideal, I know, but it would get the permissions patch over the
line and is consistent with how we currently test pg_upgrade.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-01-23 14:35:23 | Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan |
| Previous Message | Petr Jelinek | 2018-01-23 14:27:53 | Re: [PATCH] session_replication_role = replica with TRUNCATE |