> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Tuesday, April 15, 2003 12:17 PM
> To: Robert Treat
> Cc: ow; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Are we losing momentum?
>
>
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > On Tue, 2003-04-15 at 13:30, ow wrote:
> >> One of the features that PostgreSql must have, IMHO, is
> support for
> >> cross-db operations (queries, updates, deletes, inserts). 2PC and
> >> cross-server stuff would be nice but it's not as important
> as simple
> >> cross -db operations across databases on the same server.
> All major
> >> comercial RDBMS (and even mySql!) support this but for
> Postgres. Sad.
>
> > dblink ?
>
> I'm of the opinion that the availability of schemas solves
> most of the problems that people say they need cross-database
> access for. If you want cross-database access, first say why
> putting your data into several schemas in a single database
> doesn't get the job done for you.
Because you had to buy several packages to solve your problems. You
have (perhaps) Peoplesoft for HR, and SAP for CRM, Supply Chain and some
others. You bought an Oracle package for manufacturing, and you run
your web server on PostgreSQL. Nearly every large business has this
problem.
> (Obviously, this only addresses cases where you'd have put
> the multiple databases under one postmaster, but that's the
> scenario people seem to be concerned about.)
Heterogenius database access is another realistic scenario. In order to
solve this, you would need to be able to specify an ODBC, JDBC or OLEDB
table as a partner in transactions.