Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade

Поиск
Список
Период
Сортировка
Искать
От
Peter Geoghegan
Тема
Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade
Дата
Msg-id
CAH2-WzkBFgh+ZnNmL-gtPyVW4ozMreYbrVi-2Pk6kafhuX3eFA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Clarification on the release notes of postgresql 12 regarding pg_upgrade Marcelo Lacerda <marceloslacerda@gmail.com>
Re: Clarification on the release notes of postgresql 12 regardingpg_upgrade Laurenz Albe <laurenz.albe@cybertec.at>
Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade Josef Šimánek <josef.simanek@gmail.com>
Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade Peter Geoghegan <pg@bowt.ie>
Re: Clarification on the release notes of postgresql 12 regardingpg_upgrade Bruce Momjian <bruce@momjian.us>
On Fri, Oct 4, 2019 at 9:09 AM Tom Lane  wrote:
> > You can't REINDEX safely regarding that note.
>
> Actually running into that problem is quite unlikely; and if you did
> hit it, it'd just mean that the REINDEX fails, not that you have any
> urgent problem to fix.  I'd encourage you to just go ahead and REINDEX,
> if you have indexes that could benefit from the other changes.

Right. It is hard to imagine an application that evolved to fully rely
on the previous slightly higher limit, and cannot tolerate a reduction
in the limit by only 8 bytes. The limit applies to a tuple *after*
TOAST compression has been applied.

-- 
Peter Geoghegan


В списке pgsql-general по дате отправления
От: Alvaro Herrera
Дата:
От: Daniel Verite
Дата:
FAQ