> How can you guarantee that the postgres cache is coherent across machines?
When something is updated invalidation notifications are recorded.
Notifications are read and applied before each transaction.
> Also, BDB does caching in shared memory regions across multiple processes,
> so I'm not s
. Mai 2011 18:20
To: elephant-devel@common-lisp.net
Subject: Re: [elephant-devel] using one store with mutiple lisp instances
> I am curious why the postgres backend is so unpopular.
I would not recommend postgres backend as a default choice because it
has its own "peculiarities". Par
How can you guarantee that the postgres cache is coherent across machines?
Also, BDB does caching in shared memory regions across multiple processes, so
I'm not sure how much extra benefit you'll get from the Postgres cache.
Sent from my iPhone
On May 7, 2011, at 9:20 AM, Alex Mizrahi wrote:
> I am curious why the postgres backend is so unpopular.
I would not recommend postgres backend as a default choice because it
has its own "peculiarities". Particularly, it requires a discipline with
use of types, as only strings and (64-bit) integers are properly sorted.
Another major drawback
t in the mentioned scenario with BDB.But seems that we've
to rethink and test our app with postgres!
Best regards,
Lukas
> Date: Thu, 5 May 2011 12:01:40 +0200
> From: hen...@evahjelte.com
> To: elephant-devel@common-lisp.net
> Subject: Re: [elephant-devel] using one store wi
BDB.
> But seems that we've to rethink and test our app with postgres!
>
>
> Best regards,
>
> Lukas
>
>
>
> > Date: Thu, 5 May 2011 12:01:40 +0200
> > From: hen...@evahjelte.com
> > To: elephant-devel@common-lisp.net
> > Subject: Re: [e
ahjelte.com
> To: elephant-devel@common-lisp.net
> Subject: Re: [elephant-devel] using one store with mutiple lisp instances
>
> > Has anybody of you any idea or clue that could help us to use elephant with
> > Berkeley DB in the mentioned scenario, maybe an additional framework
> Has anybody of you any idea or clue that could help us to use elephant with
> Berkeley DB in the mentioned scenario, maybe an additional framework, etc.
> that could handle the locking of the shared db?
>
I am curious why the postgres backend is so unpopular. As far as I
know there is no real da
Hi Ian, hi Leslie,
thank you for comments!
> I should clarify the first sentence. With a bunch of external machinery
to support a distributed transaction model, it's possible to run BDB across
machines, but Elephant
> doesn't have any of it so can only use the built-in shared memory locking
faci
I should clarify the first sentence. With a bunch of external machinery to
support a distributed transaction model, it's possible to run BDB across
machines, but Elephant doesn't have any of it so can only use the built-in
shared memory locking facility. There was some talk a year or two ago a
BDB does not work across multiple machines, its transaction support relies on a
shared memory region to handle locking so any shared memory architecture (with
multiple CPUs) works fine but separate machines and a NAS device don't work.
You'll have to use the Postgres store (5x slower, but reaso
On Wed, May 04, 2011 at 08:37:51PM +0200, Lukas Georgieff wrote:
> well, if the points I've mentioned before are correct, I've only one
> specific question :-)
>
> We want to share a network device that contains the Berkeley-DB files.
> This BDB shall be accessed by two or more other machines that
Hi Leslie,
>Hi Lukas,
>
>> Has someone any experience using elephant in that manner?
>
>Yes -- lots in fact. But you need to ask a specific question.
well, if the points I've mentioned before are correct, I've only one
specific question :-)
We want to share a network device that contains the Ber
Hi Lukas,
> Has someone any experience using elephant in that manner?
Yes -- lots in fact. But you need to ask a specific question.
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant
14 matches
Mail list logo
