Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY

Поиск
Список
Период
Сортировка
От Vladimir Borodin
Тема Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
Дата
Msg-id 2A9246F1-28EA-4406-AC0C-D1B643DD2DEC@simply.name
обсуждение исходный текст
Ответ на Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-hackers
Дерево обсуждения

6 февр. 2017 г., в 4:57, Peter Geoghegan <pg@bowt.ie> написал(а):

I meant that I find the fact that there were no user reports in all
these years to be a good reason to not proceed for now in this
instance.

Well, we had some strange situations with indexes (see below for example) but I couldn’t even think that CIC is the problem.

And it is really difficult to give diagnostics for problems of such kind. Because 1. you may see the problem several days after last major change in the database and 2. you don’t even know how to start investigating the problem.

xdb314g/maildb M # show enable_indexscan ;
 enable_indexscan
------------------
 off
(1 row)

Time: 0.120 ms
xdb314g/maildb M #  select * from mail.folders where uid=448300241 and fid=1;
-[ RECORD 1 ]---+------------------------------
uid             | 448300241
fid             | 1
<...>

Time: 30398.637 ms
xdb314g/maildb M # set enable_indexscan to true;
SET
Time: 0.111 ms
xdb314g/maildb M #  select * from mail.folders where uid=448300241 and fid=1;
(0 rows)

Time: 0.312 ms

xdb314g/maildb M #

The row of course hasn’t been deleted.

--
May the force be with you…

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Tsunakawa, Takayuki"
Дата:
Сообщение: Re: [HACKERS] [RFC] Should I embed or parameterize syscall/Win32function names from error messages?
Следующее
От: Amit Langote
Дата:
Сообщение: Re: [HACKERS] contrib modules and relkind check