From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | A recent message added to pg_upgade |
Date: | 2023-10-27 02:57:59 |
Message-ID: | 20231027.115759.2206827438943188717.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
Attachment | Content-Type | Size |
---|---|---|
fix_messages_in_slot_c_1.patch | text/x-patch | 702 bytes |
fix_messages_in_slot_c_2.patch | text/x-patch | 687 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-10-27 03:04:47 | Re: Document parameter count limit |
Previous Message | Fujii.Yuki@df.MitsubishiElectric.co.jp | 2023-10-27 02:44:42 | RE: Partial aggregates pushdown |