From: Ricardo Wurmus <rekado@elephly.net>
To: Aljosha Papsch <aljosha.papsch@vinexus.eu>
Cc: guix-devel@gnu.org
Subject: Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass)
Date: Fri, 17 May 2019 22:29:51 +0200 [thread overview]
Message-ID: <874l5sese8.fsf@elephly.net> (raw)
In-Reply-To: <b9d7612b79aa0cfa8154f4623f831f6ae5daa9ac.camel@vinexus.eu>
Aljosha Papsch <aljosha.papsch@vinexus.eu> 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
next prev parent reply other threads:[~2019-05-18 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 21:45 Hackathon: Mumi and Cuirass Ricardo Wurmus
2019-05-04 7:19 ` Christopher Baines
2019-05-06 20:55 ` Björn Höfling
2019-05-06 22:10 ` Christopher Baines
2019-05-07 5:19 ` Ricardo Wurmus
2019-05-16 14:22 ` postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass) Giovanni Biscuolo
2019-05-17 8:26 ` Gábor Boskovits
2019-05-17 10:42 ` Aljosha Papsch
2019-05-17 20:29 ` Ricardo Wurmus [this message]
2019-05-17 12:58 ` Ricardo Wurmus
2019-05-21 10:19 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l5sese8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=aljosha.papsch@vinexus.eu \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).