Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes:
> On 7/15/16 6:13 PM, Tom Lane wrote:
>> We've talked before about how the regression tests should be circumspect
>> about what role names they create/drop, so as to avoid possibly blowing
>> up an installation's existing users during "make installcheck".
> I'm not particularly sure that that is a useful goal anymore. Setting
> up a new instance is cheap, so if users are concerned, they should not
> run the tests against their important instance.
To my mind, the main point of "make installcheck" is to verify that
your actual installation, not some other instance, is working right.
This is far from a trivial issue; for instance on a SELinux machine,
you need to be able to verify that the installed policy allows the
DB to work, and that is very likely to be path-sensitive.
So this remains an important requirement to me. It's true that it might
be something you need to run only right after making the installation ---
but that doesn't mean the DB is empty. Consider wanting to test a freshly
pg_upgrade'd installation, for example.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
