Switched to PostgreSQL
david.goodenough at linkchoose.co.uk
Thu Apr 11 16:35:45 BST 2019
On Thursday, 11 April 2019 13:07:10 BST Vojtěch Zeisek wrote:
> Dne čtvrtek 11. dubna 2019 9:39:19 CEST, Martin Steigerwald napsal(a):
> > So far the performance is really quite a bit better. The stalls during
> > filtering are gone. About the crashes I am not sure yet. Also I found
> > that there are no stalls anymore on deleting a mail.
> > Did anyone with PostgreSQL setup did any tuning on the database?
> > I see that the various PostgreSQL processes do not take all that much
> > RAM yet. They take quite a bit of RSS, but apparently share lots of it,
> > so the PSS is quite a bit lower (see in atop, memory display with "m",
> > enable PSIZE gathering with "R").
> > Is there something like mysqltuner for PostgreSQL? Otherwise I can use
> > my own training slides or official documentation.
> > However, as long as it stays as fast as it currently is, I might just
> > let the configuration alone for now.
> > Let's see how this goes.
> > Thanks again for the hint to switch to PostgreSQL and the instructions
> > for how to do it.
> Regarding PostgreSQL, I always had feeling that upgrade of PostgreSQL is not
> so straightforward as upgrade of MySQL. PostgreSQL DB must be exported,
> than cluster upgraded, settings restored and old DB imported. How do users
> of PostgreSQL and Akonadi handle this when upgrading their distribution?
I have been using Postgresql ever since Akonadi started, and the upgrade just means that
you have to remember to stop akonadi before the upgrade, then do the upgrade, and
then restart akonadi. My system takes backups every day so I never did an extra one, and
I have never needed to use the backup. I have also never needed to to anything with any
settings. This is on Debian.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kdepim-users