From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | One more question regarding dblink |
Date: | 2003-04-16 13:13:33 |
Message-ID: | 200304161843.33110.shridhar_daithankar@nospam.persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-04-16 13:46:36 | Re: [GENERAL] Problem about pgsql's column alias |
Previous Message | Jason M. Felice | 2003-04-16 13:12:50 | Re: [INTERFACES] First draft of new FE/BE protocol spec posted for comments |