SCM

[#1000677] Enhance DBLink backend interface

View Trackers | Feature Requests | Download .csv | Monitor

Date:
2006-06-27 17:09
Priority:
2
State:
Open
Submitted by:
Cristiano Duarte (cunha17)
Assigned to:
Cristiano Duarte (cunha17)
Category:
DBLink
Group:
Next Release
Related Tasks:
[T1000124] Enhance DBLink backend interface 2007-12-10 11:00 2008-12-15 11:00
Summary:
Enhance DBLink backend interface

Detailed description
Since it's not the purpose of the project, I'll place this request with a low priority.

DBLink support in Pg::Snapshot is currently implemented for Snapshot use only. I think it may be useful to have some Pg functions to interface with the internals of our DBLink. It will provide functions to query a remote database.

Why, since we already have DBLink in contrib?
The DBLink implementation in contrib puts the username and password on the query, leading to security flaws. That is, anyone with read access to a view that makes a call using dblink, can describe it and see the username and password of the remote database.

The DBLink implementation in Pg::Snapshot is almost the same used by Oracle. We store the username and password in a table(pg_dblinks - only the postgres user has access to it) along with the DBLink name. Only this name is used to perform DBLink connections.

Followup

Message
Date: 2008-12-14 13:59
Sender: Cristiano Duarte

This is an easy thing to do. So I'll implement it ASAP with high priority.

Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge