Skip site navigation (1) Skip section navigation (2)

Re: Using tables in other PostGreSQL database

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Using tables in other PostGreSQL database
Date: 2008-03-31 09:35:38
Message-ID: aaeb08be-b3c7-404e-b21d-dbf0b56dbebd@mm (view raw, whole thread or download thread mbox)
Lists: pgsql-general
	Scott Marlowe wrote:

> >  > Even in Oracle you don't have cross db queries.
> >
> >  On the contrary you do. You can refer to objects in another 
database by
> >  OBJECT_NAME(at)DBLINK_NAME, very useful to mix local and remote data 
in no
> >  time. DBLINK_NAME represents a connection to another database.
> >  What you don't have is OTHERDB.OBJECT_NAME to refer to a different
> >  database within the same instance, because there is only one 
> >  in an Oracle instance.
> What you are talking about are cross schema references, not cross db.

No I'm definitively referring to cross db, not cross schema.
See this piece from Oracle documentation: 

> Oracle instances can have > 1 database, it's just not that common.  I
> know this because we had an internal instance at the last company I
> worked at that had 2 databases in it, each with their own schemas.  
> maybe they somehow had two instances of oracle running on the same
> box.

CREATE DATABASE is to Oracle what initdb is to PG, it's something you 
do once per instance. So no, an Oracle instance doesn't have >1 
databases, just like a PG instance doesn't have >1 data directories.


 PostgreSQL-powered mail user agent and storage:

In response to


pgsql-general by date

Next:From: Craig RingerDate: 2008-03-31 10:10:26
Subject: Re: Removing redundant itemsets
Previous:From: Allan KamauDate: 2008-03-31 08:18:55
Subject: Re: Removing redundant itemsets

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group