Re: Draft back-branch release notes are up for review

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Draft back-branch release notes are up for review
Дата
Msg-id CAH2-Wz=w+byD80jb3R5hGFB9artrgn84FtSTW8z41wX6-XwX8A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Draft back-branch release notes are up for review  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sat, Jun 15, 2019 at 3:05 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thanks for the input, guys.  What do you think of
>
>      Avoid writing an invalid empty btree index page in the unlikely case
>      that a failure occurs while processing INCLUDEd columns during a page
>      split (Peter Geoghegan)
>
>      The invalid page would not affect normal index operations, but it
>      might cause failures in subsequent VACUUMs. If that has happened to
>      one of your indexes, recover by reindexing the index.

That seems perfect.

Thanks
-- 
Peter Geoghegan



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

Предыдущее
От: Oleksii Kliukin
Дата:
Сообщение: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Следующее
От: Noah Misch
Дата:
Сообщение: Re: Draft back-branch release notes are up for review