A recent message added to pg_upgade

Поиск
Список
Период
Сортировка
От Kyotaro Horiguchi
Тема A recent message added to pg_upgade
Дата
Msg-id 20231027.115759.2206827438943188717.horikyota.ntt@gmail.com
обсуждение исходный текст
Ответы Re: A recent message added to pg_upgade  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Re: A recent message added to pg_upgade  (Peter Smith <smithpb2250@gmail.com>)
Re: A recent message added to pg_upgade  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
Hello.

Some messages recently introduced by commit 29d0a77fa6 seem to deviate
slightly from our standards.

+        if (*invalidated && SlotIsLogical(s) && IsBinaryUpgrade)
+        {
+            ereport(ERROR,
+                    errcode(ERRCODE_INVALID_PARAMETER_VALUE),
+                    errmsg("replication slots must not be invalidated during the upgrade"),
+                    errhint("\"max_slot_wal_keep_size\" must be set to -1 during the upgrade"));

The message for errhint is not a complete sentence. And errmsg is not
in telegraph style.  The first attached makes minimum changes.

However, if allowed, I'd like to propose an alternative set of
messages as follows:

+                    errmsg("replication slot is invalidated during upgrade"),
+                    errhint("Set \"max_slot_wal_keep_size\" to -1 to avoid invalidation."));

The second attached does this.

What do you think about those?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Вложения

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

Предыдущее
От: "Fujii.Yuki@df.MitsubishiElectric.co.jp"
Дата:
Сообщение: RE: Partial aggregates pushdown
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Document parameter count limit