Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
Вложения
В списке pgsql-hackers по дате отправления:
| От | Heikki Linnakangas |
|---|---|
| Тема | Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum |
| Дата | |
| Msg-id | 4D6F4E5D.6080507@enterprisedb.com обсуждение исходный текст |
| Ответ на | Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum (daveg <daveg@sonic.net>) |
| Ответы |
Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum |
| Список | pgsql-hackers |
On 03.03.2011 09:12, daveg wrote: > Question: what would be the consequence of simply patching out the setting > of this flag? Assuming that the incorrect PD_ALL_VISIBLE flag is the only > problem (big assumption perhaps) then simply never setting it would at least > avoid the possibility of returning wrong answers, presumably at some > performance cost. We possibly could live with that until we get a handle > on the real cause and fix. Yes. With that assumption. If you really want to do that, I would suggest the attached patch instead. This just disables the optimization in seqscans to trust it, so an incorrectly set flag won't affect correctness of query results, but the flag is still set as usual and you still get the warnings so that we can continue to debug the issue. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера