Re: SQL/MED compatible connection manager - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SQL/MED compatible connection manager
Date
Msg-id 493E98E9.3070507@gmx.net
Whole thread Raw
In response to Re: SQL/MED compatible connection manager  (Martin Pihlak <martin.pihlak@gmail.com>)
Responses Re: SQL/MED compatible connection manager  (Martin Pihlak <martin.pihlak@gmail.com>)
Re: SQL/MED compatible connection manager  (Martin Pihlak <martin.pihlak@gmail.com>)
List pgsql-hackers
Martin Pihlak wrote:
> Peter Eisentraut wrote:
>> If I read this right, SQL/MED requires option names to be unique for a
>> server.  To this needs to be rethought.
>>
>
> Attached is another revision of the connection manager, notable changes:

Attached is my current patch after surgery.  I have mainly worked on
making naming better and more consistent.

Problem: You have implemented foreign-data wrappers and foreign servers
as schema-qualified objects, but the standard has them outside schemas,
qualified only optionally by catalogs (a.k.a. databases).  I think that
should be fixed.

Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Multiplexing SUGUSR1
Next
From: Gregory Stark
Date:
Subject: Re: contrib/pg_stat_statements 1202