Currently pl/proxy, dblink, DBI-link etc. each have their own remote connection
info management infrastructure (or none at all). It would certainly help if
they could use a common connection database -- with access control, pg_dump
support, etc. There have been hints that a SQL/MED compatible connection
manager would be desirable:
So the proposal is to implement a small subset of SQL/MED to cope with
connection info management -- connection manager. This will only manage the
connection metadata and provide the required system catalogs and commands for
maintaining them. The actual connection management (open/close etc.) is still
handled by the client modules.
I have put together a draft that describes a possible implementation:
Tons of details have been omitted, but should be enough to start discussion.
What do you think, does this sound usable? Suggestions, objections?
pgsql-hackers by date
|Next:||From: Jonah H. Harris||Date: 2008-10-27 14:35:14|
|Subject: Re: SQL/MED compatible connection manager|
|Previous:||From: Robert Haas||Date: 2008-10-27 13:54:40|
|Subject: Re: WIP patch: convert SQL-language functions to return tuplestores|