pgsql: Use a consistent error message style for user mappings.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use a consistent error message style for user mappings.
Date: 2017-03-20 20:07:45
Message-ID: E1cq3aj-0006Tl-V9@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use a consistent error message style for user mappings.

User mappings are essentially anonymous, so messages referring to "user
mapping foo on server bar" are wrong, and inconsistent with other error
messages referring to user mappings. To be consistent with existing use,
use "user mapping for foo on server bar" instead.

I dropped the noise word "user" from the original suggestion to be
consistent with other uses.

Discussion: http://postgr.es/m/56c6f8ab-b2d6-f1fa-deb0-1d18cf67f7b9@2ndQuadrant.com

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/839cb0649a9f595a8534cdf14afbe89efb1757b1

Modified Files
--------------
src/backend/commands/foreigncmds.c | 8 ++++----
src/test/regress/expected/foreign_data.out | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2017-03-20 20:50:54 pgsql: Add IF NOT EXISTS for CREATE SERVER and CREATE USER MAPPING
Previous Message Robert Haas 2017-03-20 19:58:24 pgsql: Another fix for single-page hash index vacuum.