One more question regarding dblink - Mailing list pgsql-hackers

From Shridhar Daithankar
Subject One more question regarding dblink
Date
Msg-id 200304161843.33110.shridhar_daithankar@nospam.persistent.co.in
Whole thread Raw
Responses Re: One more question regarding dblink  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Hi,

I know I should have clubbed in last post but did not notice.

1. Why is that dblink allows only one persistent connection? It should allow 
more than one persistent connections to same or different databases, 
searchable by name. Of course we do not expect number of remote connection to 
be huge. So a simple structure would suffice.

2. To create a persistent connection, one has to call dblink_connect 
explicitly. Oracle allows a database link connection to be part of database 
schema. Hence when a database comes up it brings the database link up as 
well.

Is there an equivalent of .profile/.logout  per database/per schema/per table 
in postgresql? That should be an ideal place to put a database link 
initiation/termination.

Should be a nifty addtion. I don't know how practical that sounds to core 
developers.
Shridhar



pgsql-hackers by date:

Previous
From: Shridhar Daithankar
Date:
Subject: DBLink cursors
Next
From: "Jason M. Felice"
Date:
Subject: Re: [INTERFACES] First draft of new FE/BE protocol spec posted for comments