Recently-introduced segfault in initdb?
От | Isaac Morland |
---|---|
Тема | Recently-introduced segfault in initdb? |
Дата | |
Msg-id | CAMsGm5cF67Hs1WEGYOkVsEDWtF5RacEOfndf_e7u52DFPeg2yQ@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: Recently-introduced segfault in initdb?
|
Список | pgsql-hackers |
1733460f0205fc6d6bbe4c14911049a918c6e073 is the first bad commit
commit 1733460f0205fc6d6bbe4c14911049a918c6e073
Author: Robert Haas <rhaas@postgresql.org>
Date: Fri Mar 2 13:16:01 2018 -0500
postgres_fdw: Fourth attempt to stabilize regression tests.
Commit 1bc0100d270e5bcc980a0629b8726a32a497e788 added this test, and
commits 882ea509fe7a4711fe25463427a33262b873dfa1,
958e20e42d6c346ab89f6c72e4262230161d1663,
4fa396464e5fe238b7994535182f28318c61c78e tried to stabilize it. It's
still not stable, so keep trying.
The latest comment from Tom Lane is that disabling autovacuum seems
like a good strategy, but we might need to do it on more tables, hence
this patch.
Etsuro Fujita
Discussion: http://postgr.es/m/5A9928F1.2010206@lab.ntt.co.jp
:040000 040000 97d2b695bc44dd6c50ccc2c73e626ae453507299 c3e23dd08d4f9d0576401d63e375cbb3460e2d33 M contrib
bisect run success
01:01 ijmorlan@scsmac161$
В списке pgsql-hackers по дате отправления: