> 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
Hi,
since the last mails I am are working on an idea of a federated DB - so we
would use two separate DBs on two machines.
The application is designed to synchronize the stored data over Atom Feeds
(not because of the last problem, but as a main feature of the app).
Since it is not critical to be
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
