Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11
| От | Melanie Plageman |
|---|---|
| Тема | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |
| Дата | |
| Msg-id | CAAKRu_Z+oeQW2NqqfiCmxv8nq+4MVWFzimJQobZGB-AhQzw68A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11
|
| Список | pgsql-hackers |
On Mon, Jul 8, 2019 at 12:21 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
The point of regressplans.sh is to see if anything goes seriously
wrong when forcing non-default plan choices --- seriously wrong being
defined as crashes or semantically wrong answers. It's not expected
that the regression tests will automatically pass when you do that,
because of their dependencies on output row ordering, not to mention
all the EXPLAINs. I'm not for removing it --- the fact that its
results require manual evaluation doesn't make it useless.
It might be worth post-processing results files to ignore row ordering
in some cases to allow for easier comparison. Has this been proposed
in the past?
in some cases to allow for easier comparison. Has this been proposed
in the past?
--
Melanie Plageman
В списке pgsql-hackers по дате отправления: