Date: Sat, 5 Jun 1999 01:44:37 -0300 (ADT) From: The Hermit Hacker <scrappy@hub.org> To: Eivind Eklund <eivind@freebsd.org> Cc: chat@freebsd.org Subject: Re: Sun Spurs Innovation in Supercomputing Message-ID: <Pine.BSF.4.05.9906050142310.413-100000@thelab.hub.org> In-Reply-To: <19990604064554.B80950@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Jun 1999, Eivind Eklund wrote:
> On Fri, Jun 04, 1999 at 01:40:36AM -0300, The Hermit Hacker wrote:
> > On Fri, 4 Jun 1999, Eivind Eklund wrote:
> > > Replacing the lock calls with calls to an API for a distributed lock
> > > manager. This allowed the use of PostgreSQL in high-availability
> > > clusters, with two machines sharing the same physical "disk"
> > > (actually, RAID array).
> >
> > Not quick sure how this applies (if it even does), but v6.5 of PostgreSQL
> > has had major changes done to it on its 'concurrency' code, to improve
> > locking...but I'm suspecting that its not 'client' locking you are talking
> > about here?
>
> No, it is not. I'm talking about using the same physical postgresql
> database with two concurrent postgresql processes running against it
> (the two different processes are on different machines, but the
> database is on shared physical media). Am I being clear now?
Okay, totally understood now.
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906050142310.413-100000>