Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Дата
Msg-id 1255.1348076851@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.  (Simon Riggs <simon@2ndQuadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
BTW, what should our advice be for recovering from corruption due to
this bug?  As far as the btree and GIN problems go, we can tell people
that REINDEX will fix it.  And in 9.1, you don't really need to worry
about the visibility map being bad.  But what do you do in 9.2, if
you have a bad visibility map?  Is there any fix short of VACUUM FULL?
        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Invalid optimization of VOLATILE function in WHERE clause?
Следующее
От: Noah Misch
Дата:
Сообщение: Re: Removal of AcceptInvalidationMessages broke things