Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Simon Pills: "Someone finally invented an intuitively used and easily customized PostgreSQL database administration tool! Keep up the good work. I will be in touch. I am able to do this horrendous work because your software enabled me to create a new database with all necessary objects in several minutes! I am sure that I have found what I really need".
Armin Braunstein: "Also I must say, that your PostgreSQL Maestro tool is the best tool for PostgreSQL I have seen. For general I am really happy about the tool and how it works".

More

Add your opinion

PostgreSQL Maestro online Help

Prev Return to chapter overview Next

User Mappings

A user mapping typically encapsulates connection information that a foreign-data wrapper uses together with the information encapsulated by a foreign server to access an external data resource. The owner of a foreign server can create user mappings for that server for any user. Also, a user can create a user mapping for his own user name if USAGE privilege on the server has been granted to the user.

 

Name

The name of an existing user that is mapped to foreign server. CURRENT_USER and USER match the name of the current user. When PUBLIC is specified, a so-called public mapping is created that is used when no user-specific mapping is applicable.

 

Options

This clause specifies the options of the user mapping. The options typically define the actual user name and password of the mapping. Option names must be unique. The allowed option names and values are specific to the server's foreign-data wrapper. Note that only superusers may connect to foreign servers without password authentication, so always specify the password option for user mappings belonging to non-superusers. The screenshot below shows an example of user mapping options.

 



Prev Return to chapter overview Next