Just my two cents on the issue:
A good reason would be having several databases which
each use the same set of tables which contain some information
which takes a lot of storage, such as dictionaries or map
information. You wouldn't want to maintain several copies
of 500 Mb tables, especially if they get updated frequently.
The workaround, for now, is to have a table just for the
foreign keys for the different systems, and to query the
shared database separately from within your programming
environment.
Troy
>
>
> "Douglas Rafael da Silva" <douglas@inducola.com.br> schrieb im Newsbeitrag
> news:3BCF859C.D42C8895@inducola.com.br...
> > Hi,
> >
> > I'd like to do a query where can be possible I access tables from
> > diferent databases on the same query.
> > On MySQL, I do:
> >
> > But Who I can to do this on Postgresql ?
>
> You CANNOT do that with PostgreSQL.
> But why do you want to do that? IMHO it's a rather bas design to hold data
> in different places, if you need to select them in one query.
> Is there a real reason to hold the tables in different databases?
>
> Andre
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>