pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Hans-Jürgen Schönig <postgres@cybertec.at>
Cc: pgsql-hackers@postgresql.org, EG <EG@cybertec.at>
Subject: Re: dblink_ora - a first shot on Oracle ...
Date: Mon, 21 Jul 2003 07:48:22 -0700
Message-ID: <3F1BFD36.70200@joeconway.com> (raw)
In-Reply-To: <4455.1058796993@sss.pgh.pa.us>
References: <200307211339.h6LDdTR00206@candle.pha.pa.us>
	<4455.1058796993@sss.pgh.pa.us>

Tom Lane wrote:
> I tend to agree with Peter: if dblink is going to start depending on
> stuff outside Postgres, it ought to be become a separate project,
> if only to simplify distribution and configuration issues.
> 
> Perhaps it could be split into two parts, a PG-specific part and
> a cross-DBMS part?
> 
> 			regards, tom lane
> 
> PS: Has anyone looked any further at the SQL-MED standard?  ISTM that's
> where we ought to head in the long run.

I think for that very reason (SQL-MED) we need to come to terms with 
this issue. If/when connections to external data sources is in the 
backend, you'll have those exact same dependencies. And in fact, we do 
today: consider '--with-openssl' or '--with-tcl'.

I had always assumed we would need '--with-oracle', '--with-jdbc',  etc 
(or whatever you want to call them) to support backend connections to 
external sources. And this discussion is the very reason I was hesitant 
to pursue dblink_ora or jdbclink now, because I didn't think people 
would be comfortable with configure options to support a contrib library.

Joe




view thread (28+ messages)  latest in thread

Message-ID: <3F1BFD36.70200@joeconway.com>
Permalink:  ../3F1BFD36.70200@joeconway.com/
Also on:    postgresql.org/message-id/3F1BFD36.70200@joeconway.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: mail@joeconway.com, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, peter_e@gmx.net, postgres@cybertec.at, EG@cybertec.at
  Subject: Re: dblink_ora - a first shot on Oracle ...
  In-Reply-To: <3F1BFD36.70200@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox