Re: SQL/MED compatible connection manager

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SQL/MED compatible connection manager
Date: 2009-01-05 13:32:52
Message-ID: 49620C04.8070708@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martin Pihlak wrote:
>> I would call it something like
>>
>> pg_postgresql_fdw_options_string(server, user) returns text
>
> Hmm, it is probably a good idea to avoid the fdw abbreviation -- the term
> "foreign data wrapper" is already confusing enough. My suggestion:
>
> pg_foreign_server_conninfo(server)
> pg_foreign_server_conninfo(server,user)
>
> If there are no objections, I'll whack those functions out, and bring the dblink
> patch up to date.

Sure, propose some code. (Note that you can use parameter default
values now.)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-05 13:46:52 EmitWarningsOnPlaceholders is too quiet
Previous Message Zdenek Kotala 2009-01-05 12:33:17 Re: version() output vs. 32/64 bits