Re: [HACKERS] Shared tables

From: Brandon Ibach <bibach(at)infomansol(dot)com>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: hackers(at)postgresql(dot)org (PostgreSQL Hackers)
Subject: Re: [HACKERS] Shared tables
Date: 1998-02-17 10:02:05
Message-ID: 199802171002.EAA06219@vweb.infomansol.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas G. Lockhart said:
>
> > Do we have a way, at the moment, supported or otherwise, to "share"
> > tables across multiple databases? For instance, some of the catalogs
> > are the same from one database to another, but could I create a new
> > table and share it (and possibly some indexes on it) between more than
> > one database?
>
> No, that is not directly supported by the backend. You might be able to
> do some trickery using soft links...
>
> Also, I've been thinking about what it would take to allow the backend to
> connect to another backend as a client. 'Course, I don't know much about
> it, but it would be neat to be able to do...
>
Sounds interesting... :) As for table sharing, I could do hard or
soft links, but the question is, would that create the potential for
Postgres corrupting things, given that it isn't wise to the situation,
and could therefore defeat its own locking mechanisms? Of course,
this would probably just be a read-only table (just some data I'd like
to have access to from multiple databases), so I could probably get
away with just creating the links. Anybody have a reason against
this?

-Brandon :)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim B. Mikheev 1998-02-17 10:24:43 Re: [HACKERS] Re: [QUESTIONS] trouble grouping rows
Previous Message Zeugswetter Andreas SARZ 1998-02-17 09:34:37 Re: Subselects open issue Nr. NEW