Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6
От | Tom Lane |
---|---|
Тема | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |
Дата | |
Msg-id | 28030.1557240619@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: REINDEX INDEX results in a crash for an index of pg_class since9.6 (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: REINDEX INDEX results in a crash for an index of pg_class since9.6
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > I for sure thought I earlier had an idea that'd actually work. But > either I've lost it, or it didn't actually work. But perhaps somebody > else can come up with something based on the above strawman ideas? Both of those ideas fail if an autovacuum starts up after you're done looking. I still think the only way you could make this reliable enough for the buildfarm is to do it in a TAP test that's set up a cluster with autovacuum disabled. Whether it's worth the cycles to do so is pretty unclear, since that wouldn't be a terribly real-world test environment. (I also wonder whether the existing TAP tests for reindexdb don't provide largely the same coverage.) My advice is to let it go until we have time to work on getting rid of the deadlock issues. If we're successful at that, it might be possible to re-enable these tests in the regular regression environment. regards, tom lane
В списке pgsql-hackers по дате отправления: