Re: Rethinking opclass member checks and dependency strength
| От | Hamid Akhtar |
|---|---|
| Тема | Re: Rethinking opclass member checks and dependency strength |
| Дата | |
| Msg-id | 159594787542.781.16030655391691281794.pgcf@coridan.postgresql.org обсуждение исходный текст |
| Ответ на | Re: Rethinking opclass member checks and dependency strength (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>) |
| Ответы |
Re: Rethinking opclass member checks and dependency strength
|
| Список | pgsql-hackers |
The following review has been posted through the commitfest application: make installcheck-world: tested, failed Implements feature: tested, failed Spec compliant: not tested Documentation: not tested I've gone through the patch and applied on the master branch, other than a few hunks, and whether as suggested upthread,the default case for "switch (op->number)" should throw an error or not, I found that bloom regression is crashing. ------------- test bloom ... FAILED (test process exited with exit code 2) 20 ms +server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. +connection to server was lost ------------- The new status of this patch is: Waiting on Author
В списке pgsql-hackers по дате отправления: