| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josef Šimánek <josef(dot)simanek(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Marcelo Lacerda <marceloslacerda(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade |
| Date: | 2019-10-04 16:09:19 |
| Message-ID: | 14924.1570205359@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef(dot)simanek(at)gmail(dot)com> writes:
> But the problem in this case is probably this note:
>> This means that a REINDEX
>> <https://www.postgresql.org/docs/12/sql-reindex.html> operation on an
>> index pg_upgrade'd from a previous release could potentially fail.
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-10-04 16:28:43 | Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparent wraparound |
| Previous Message | Moreno Andreo | 2019-10-04 16:01:15 | Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparent wraparound |