From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Warnings around booleans |
Date: | 2015-08-21 17:47:34 |
Message-ID: | CAOuzzgo4rnLi1g=DYL0Krq7DV7dhqd5Go+P7ULdKck9aqPTC7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday, August 21, 2015, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stephen Frost <sfrost(at)snowman(dot)net <javascript:;>> writes:
> > On Friday, August 21, 2015, Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me
> <javascript:;>>
> > wrote:
> >> If I'm not mistaken, the roles introduced in this test are never
> dropped,
> >> which will cause the test to fail on consequent runs.
>
> > Ah, I was thinking there was a reason to not leave them around but
> couldn't
> > think of it and liked the idea of testing the pg_dumpall / pg_upgrade
> code
> > paths associated.
>
> > Perhaps the way to address this is to add a bit of code to drop them if
> > they exist? That would be reasonably straight-forward to do, I believe.
>
> It is not really acceptable to leave roles hanging around after "make
> installcheck"; that would be a security hazard for the installation.
> Please drop them.
>
The only ones which were left were intentionally all NOLOGIN to address
that concern, which I had considered. Is there another issue with them
beyond potential login that I'm missing?
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-08-21 17:55:00 | Re: Using quicksort for every external sort run |
Previous Message | Tom Lane | 2015-08-21 17:42:53 | Re: Warnings around booleans |