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

SQL/MED compatible connection manager

From: Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: SQL/MED compatible connection manager
Date: 2008-10-27 14:06:03
Message-ID: 4905CACB.7060708@gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Howdy,

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:
http://archives.postgresql.org/pgsql-hackers/2008-09/msg00314.php
http://archives.postgresql.org/pgsql-hackers/2008-09/msg00909.php

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:
http://wiki.postgresql.org/wiki/SqlMedConnectionManager

Tons of details have been omitted, but should be enough to start discussion.
What do you think, does this sound usable? Suggestions, objections?

thanks,
Martin


Responses

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2008-10-27 14:35:14
Subject: Re: SQL/MED compatible connection manager
Previous:From: Robert HaasDate: 2008-10-27 13:54:40
Subject: Re: WIP patch: convert SQL-language functions to return tuplestores

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