Re: pgsql: Switch TAP tests of pg_rewind to use a role with minimal permiss

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Switch TAP tests of pg_rewind to use a role with minimal permiss
Date: 2019-04-14 10:21:15
Message-ID: 20190414102115.GA4737@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Apr 13, 2019 at 11:12:25AM -0400, Alvaro Herrera wrote:
> I'm not sure that reverting and re-committing a slightly improved patch
> is a better approach than just waiting for the (presumably small) fix to
> be committed. Leaving a small number of animals in red for a small
> period is not that bad.

Thanks, however I am not so sure when it comes to Windows failures as
these can prove to need tricky treatments. Anyway, there is a daily
commit activity and it is always annoying to bump on failures from
others and this could hide other problems. 947a350 and 9daefff are
for example two things from Noah which refer to jacana and have een
committed in-between, so reverting temporarily was still the best
thing to do I think.

I have committed the fixed version of this patch, after making sure
that the test is able to work on Windows, and that this does not
impact what we want to test: if one of the GRANT queries is removed
the test fails properly.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Piotr Stefaniak 2019-04-14 19:59:46 Re: pgsql: Increase upper limit for vacuum_cleanup_index_scale_factor
Previous Message Michael Paquier 2019-04-14 09:52:25 pgsql: Switch TAP tests of pg_rewind to use non-superuser role, take tw