| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | SQL/MED spec for cross-database linkages |
| Date: | 2002-12-06 16:04:58 |
| Message-ID: | 10719.1039190698@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe, have you heard of a standard called SQL/MED? I came across a
description of it the other day. You might think it's got some medical
connotation, but actually the acronym is Management of External Data,
and what it is is a standard spec for shipping chunks of SQL queries to
remote servers. For instance, given
SELECT * FROM a.foo, b.bar WHERE ...
where a.foo is on a remote machine, the spec lays down how the local and
remote servers can cooperate to execute this query intelligently ---
including deciding where to execute various WHERE clauses to minimize
the amount of data shipped. (The article I found was actually about
how the new draft version of SQL/MED improves the protocol to let this
sort of thing be done better; it seems the original spec only allowed
retrieval of a whole table's contents.)
This looks like it might be a great long-term replacement for dblink,
and if it is standard, so much the better.
I imagine the draft version of the new SQL/MED spec may be available on
the web, but haven't gone looking.
Just a heads-up in case you are interested...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-12-06 16:35:25 | Re: SQL/MED spec for cross-database linkages |
| Previous Message | Igor Georgiev | 2002-12-06 15:59:31 | Re: Postmaster windows shell |