Skip site navigation (1) Skip section navigation (2)

Re: SQL/MED - core functionality

From: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
To: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
Cc: Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SQL/MED - core functionality
Date: 2010-12-01 05:22:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
2010/12/1 Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>:
> On Wed, Dec 1, 2010 at 12:30, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> wrote:
>> From a user's view, this is very long way to see a simplest foreign
>> table. I know it is based on the standard, but I really want a
>> shortcut. Especially, I don't understand why CREATE USER MAPPING FOR
>> current_user SERVER <server> is needed for default use case. If you
>> forget CREATE USER MAPPING and do CREATE FOREIGN TABLE, it raises an
>> error. User mapping is useful if the local user and remote user should
>> be mapped but I imagine in most cases they are the same.
>> postgresql_fdw can tell the remote user by conninfo string, in
>> addition.
> How do you connect to the remote server when password is required?
> I think we cannot pass through passwords to the remote server
> even if the same user is used on the local and remote servers.

Sure, it is limited on trust authentication only. If you need more
complicated connection, do USER MAPPING. But it's not clear to me that
it should be required in any case.


Hitoshi Harada

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-12-01 05:31:34
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4
Previous:From: Peter EisentrautDate: 2010-12-01 05:14:56
Subject: Re: profiling connection overhead

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group