[Mailman3-dev] Re: [Mailman-Developers] Debate about Mailman on BytesForAll

Richard Barrett r.barrett at openinfo.co.uk
Fri Aug 27 17:22:24 CEST 2004


On 27 Aug 2004, at 13:54, Ian Eiloart wrote:

>
>
> --On Thursday, August 26, 2004 4:13 pm -0400 Barry Warsaw 
> <barry at python.org> wrote:
>
>> (Redirecting to the Mailman 3 list)
>>
>> On Thu, 2004-08-26 at 16:10, Dale Newfield wrote:
>>> On Thu, 26 Aug 2004, Barry Warsaw wrote:
>>> > I've been thinking that, what with all the problems associated with
>>> > BerkeleyDB, it might not make sense to switch to SQLite as the
>>> > embedded, default database for MM3.
>>>
>>> The biggest problem with BerkeleyDB is that it REQUIRES that the file
>>> system support memory mapping the files.  This means that you cannot
>>> guarantee correctness if these files are located on an NFS mount.
>>>
>>> http://www.sleepycat.com/docs/ref/env/remote.html
>>
>> Add that to the list of BDB problems, then. :/
>>
>> -Barry
>>
>
> I've been looking at the SQLite site here 
> <http://www.sqlite.org/cvstrac/wiki?p=WhenToUseSqlite>. They recommend 
> that you don't use SQLite on NFS mounted file systems - for the same 
> reasons.

Postgresql concurrency control is described here and so far as I m 
aware does not preclude the use NFS mounted storage as it does not 
depend on file system locking:

http://www.postgresql.org/docs/7.4/static/mvcc.html

>
> -- 
> Ian Eiloart
> Servers Team
> Sussex University ITS



More information about the Mailman3-Dev mailing list