| От | Amit Langote |
|---|---|
| Тема | Re: Partitioned tables and covering indexes |
| Дата | |
| Msg-id | 994fa677-2dac-8fe5-3f39-024cd6406522@lab.ntt.co.jp обсуждение |
| Ответ на | Re: Partitioned tables and covering indexes (Teodor Sigaev <teodor@sigaev.ru>) |
| Ответы |
Re: Partitioned tables and covering indexes
Re: Partitioned tables and covering indexes |
| Список | pgsql-hackers |
Hi. On 2018/04/11 0:36, Teodor Sigaev wrote: >> Does the attached fix look correct? Haven't checked the fix with >> ATTACH >> PARTITION though. >> >> >> Attached patch seems to fix the problem. However, I would rather get >> rid of modifying stmt->indexParams. That seems to be more logical >> for me. Also, it would be good to check some covering indexes on >> partitioned tables. See the attached patch. > > Seems right way, do not modify incoming object and do not copy rather > large and deep nested structure as suggested by Amit. Yeah, Alexander's suggested way of using a separate variable for indexParams is better. > But it will be better to have a ATTACH PARTITION test too. I have added tests. Actually, instead of modifying existing tests, I think it might be better to have a separate section at the end of indexing.sql to test covering indexes feature for partitioned tables. Attached find updated patch. Thanks, Amit
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера