From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Regression tests vs existing users in an installation |
Date: | 2019-11-26 21:10:15 |
Message-ID: | 499f2909-d6e4-4f50-d88a-0e3dc9530f4e@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-06-29 19:21, Tom Lane wrote:
> Stephen Frost<sfrost(at)snowman(dot)net> writes:
>> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>>> We could make the new subdirectory be something specific like
>>> "src/test/modules/test_rolenames", but I think very likely we'll be
>>> wanting some additional test scripts that we likewise deem unsafe to
>>> run during "installcheck". So I'd rather choose a more generic module
>>> name, but I'm not sure what ... "unsafe_tests"?
>> Agreed but haven't got any particularly good suggestions on names..
> Hearing no better suggestions, I went with "unsafe_tests" in the
> attached.
I found this directory, and it seems like a good place to add some more
tests (other thread), but I'm puzzled why it's hidden under modules/,
since it's not, well, a module. Why is it not in src/test/?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2019-11-26 21:38:06 | Re: Collation versions on Windows (help wanted, apply within) |
Previous Message | Thomas Munro | 2019-11-26 20:43:21 | Re: Collation versioning |