Re: [HACKERS] some dblink refactoring
От
Peter Eisentraut
Тема
Re: [HACKERS] some dblink refactoring
Дата
Msg-id
140df28a-bdba-e5ec-9d55-54697e42e71e@2ndquadrant.com
Ответ на
Re: [HACKERS] some dblink refactoring (Corey Huinker)
Список
Дерево обсуждения
[HACKERS] some dblink refactoring Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] some dblink refactoring "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
Re: [HACKERS] some dblink refactoring "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
Re: [HACKERS] some dblink refactoring Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] some dblink refactoring Corey Huinker <corey.huinker@gmail.com>
Re: [HACKERS] some dblink refactoring Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
On 2/28/17 22:22, Corey Huinker wrote: > Any chance we can make get_connect_string() a core function or at least > externally accessible? [get_connect_string() gets the connection string for a foreign server] The connection string for a foreign server depends on the nature of the foreign server. dblink can assume it's a PostgreSQL server, but it's not clear how to generalize that. Some kind of node or connection registry (i.e., "native" servers) might be a better feature to think about here. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления