[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuiras
From: |
Ricardo Wurmus |
Subject: |
Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass) |
Date: |
Fri, 17 May 2019 22:29:51 +0200 |
User-agent: |
mu4e 1.2.0; emacs 26.2 |
Aljosha Papsch <address@hidden> writes:
> Am Freitag, den 17.05.2019, 10:26 +0200 schrieb Gábor Boskovits:
>> Any suggestions to overcome this would be appreciated.
>
> I would go with the client/server database. It helps scaling in the
> long term and Guix must take over the world, no? With SQLite you'll be
> stuck with the single file on a single server. You could implement your
> custom replication using rsync or whatever, but you'll have to ensure
> that the receivers do not write to the file (readonly "slaves"). In the
> end it will be a problem already solved by Postgres and other
> server/client databases.
Our current problem is not replication and we’re far from needing it at
this point. I think there are better ways to improve Cuirass than to
switch to Postgres.
--
Ricardo
- Hackathon: Mumi and Cuirass, Ricardo Wurmus, 2019/05/03
- Re: Hackathon: Mumi and Cuirass, Christopher Baines, 2019/05/04
- Re: Hackathon: Mumi and Cuirass, Björn Höfling, 2019/05/06
- Re: Hackathon: Mumi and Cuirass, Christopher Baines, 2019/05/06
- Re: Hackathon: Mumi and Cuirass, Ricardo Wurmus, 2019/05/07
- postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass), Giovanni Biscuolo, 2019/05/16
- Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass), Ricardo Wurmus, 2019/05/19
- Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass), Ludovic Courtès, 2019/05/21