| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_rewind vs superuser |
| Date: | 2019-04-11 04:14:46 |
| Message-ID: | 20190411041446.GN2728@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 09, 2019 at 10:38:19AM +0900, Michael Paquier wrote:
> Sure. With something like the attached? I don't think that there is
> much point to complicate the test code with multiple roles if the
> default is a superuser.
As this topic differs from the original thread, I haev started a new
thread, so let's discuss the proposed patch there:
https://www.postgresql.org/message-id/20190411041336.GM2728@paquier.xyz
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-04-11 04:22:28 | Re: block-level incremental backup |
| Previous Message | Michael Paquier | 2019-04-11 04:13:36 | Switch TAP tests of pg_rewind to use role with only function permissions |