Unify a recently-added inconsisnt message
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2025-03-17T04:53:05Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Unify wording of user-facing "row security" messages.
- ed762e94253d 18.0 landed
-
pg_dump, pg_dumpall, pg_restore: Add --no-policies option.
- cd3c45125d2d 18.0 cited
Attachments
- 0001-Unify-wording-of-user-facing-row-security.patch (text/x-patch)
Subject: Unify a recent-added inconsisnt message
Hello.
I noticed that the recent commit cd3c45125d2 introduced the following
three inconsistent messages at the same time:
pg_dump.c:
+ printf(_(" --no-policies do not dump row security policies\n"));
pg_dumpall.c:
+ printf(_(" --no-policies do not dump row security policies\n"));
pg_restore.c:
+ printf(_(" --no-policies do not restore row level security policies\n"));
The existing user-facing messages commonly use "row security".
Therefore, I believe the newly introduced message should follow the
same wording for consistency.
Please find the attached patch that updates the inconsistent message.
--
Kyotaro Horiguchi
NTT Open Source Software Center