Re: A recent message added to pg_upgade

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: A recent message added to pg_upgade
Дата
Msg-id CAA4eK1Jo2PP6mRHTscoiURqpa9vWXPkeMHKP47HrM8DwcKPBTA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: A recent message added to pg_upgade  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: A recent message added to pg_upgade  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On Fri, Nov 10, 2023 at 7:50 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Nov 09, 2023 at 04:52:32PM +0900, Michael Paquier wrote:
> > Thanks!
>
> Also, please see also a patch about switching the logirep launcher to
> rely on IsBinaryUpgrade to prevent its startup.  Any thoughts about
> that?
>

Preventing these
+ * processes from starting while upgrading avoids any activity on the new
+ * cluster before the physical files are put in place, which could cause
+ * corruption on the new cluster upgrading to.

I don't think this comment is correct because there won't be any apply
activity on the new cluster as after restoration subscriptions should
be disabled. On the old cluster, I think one problem is that the
origins may move forward after we copy them which can cause data
inconsistency issues. The other is that we may not prefer to generate
additional data and WAL during the upgrade. Also, I am not completely
sure about using the word 'corruption' in this context.

--
With Regards,
Amit Kapila.



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

Предыдущее
От: jian he
Дата:
Сообщение: Re: Add the ability to limit the amount of memory that can be allocated to backends.
Следующее
От: ZIMANYI Esteban
Дата:
Сообщение: Parallel aggregates in PG 16.1