Re: [HACKERS] More CORBA and PostgreSQL

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Michael Robinson <robinson(at)public(dot)bta(dot)net(dot)cn>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] More CORBA and PostgreSQL
Date: 1998-11-13 14:49:53
Message-ID: 364C4711.3321AE7F@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I don't know what is implemented, but check out:
> http://www.vsb.cs.uni-frankfurt.de/~mico
> They "claim" a completely 2.2 Corba implementation...

If someone were choosing an ORB, they perhaps could look at whatever the
Gnome project chose (either mico or ORBit, can't remember which). Also,
they didn't consider ILU because of licensing considerations, but the
license changed very recently and I think would now be a strong
candidate...

> > ... the PostgreSQL backend
> > doesn't seem ready for it. In particular, it doesn't appear to be
> > thread safe. It may not even be reentrant, from what I can tell.
> > And, if a backend process is not punctual about reading cache
> > synchronization messages out of the IPC queue, it appears that
> > excessive cache invalidation would hurt performance.

The PG backend is neither reentrant nor threadsafe, and isn't likely to
become so soon (several/many places where global variables are used,
etc).

However, with the existing "forked model", there is a separate backend
for each client, so (if I understand things a bit) the trick will be
figuring out how to call a single routine which will give access to a
client (as happens now) but without handing off through a socket/IP
connection.

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-11-13 14:54:24 Re: [HACKERS] More CORBA and PostgreSQL
Previous Message David Ben-Yaacov 1998-11-13 14:08:09 High-level of inserts makes database drop core