user mapping messages - Mailing list pgsql-hackers

From Andrew Dunstan
Subject user mapping messages
Date
Msg-id 56c6f8ab-b2d6-f1fa-deb0-1d18cf67f7b9@2ndQuadrant.com
Whole thread Raw
List pgsql-hackers
While reviewing the IF NOT EXISTS patch for CREATE USER MAPPING I
noticed that in several places we treat the user name as the name of the
user mapping. Strictly ISTM that user mappings are really anonymous
objects, so instead of something like user "mapping \"%s\" does not
exist for the server" we should possibly have "user mapping for user
\"%s\" does not exist for the server". I was about to make that change
in the patch when I saw that it was consistent with current usage. Do we
want to stick with the current usage where we treat the user name as the
mapping name, or change it?


(Yes, I know, it's pretty trivial).


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Make subquery alias optional in FROM clause
Next
From: "Dr. Michael Meskes"
Date:
Subject: Re: [HACKERS] Keep ECPG comment for log_min_duration_statement