Ok thanks I will try that.
But do you know if there is any way to avoid this?
vm.swapiness? or anything on the postgres conf?
Il giorno mar 16 ott 2018 alle ore 15:17 Bob Jolliffe
ha scritto:
> I guess you can run swapoff (followed by swapon). That will free up
> whatever is currently swapped.
I guess you can run swapoff (followed by swapon). That will free up
whatever is currently swapped. Beware if the system is actively
swapping then swapoff can take some time. But it seems not in your
case.
On Tue, 16 Oct 2018 at 10:48, Nicola Contu wrote:
>
> No it is not probably used, because
No it is not probably used, because I can't find it in any way as I said.
I run your commands :
[root@usnyh-cmd1 ~]# vmstat 1
procs ---memory-- ---swap-- -io -system--
--cpu-
r b swpd free buff cache si sobibo in cs us sy id
wa st
3 2 750
Nicola Contu wrote:
> we are running Postgres 10.5 with master slave replication.
>
> This server is on Centos 7 and the strange thing is that we see a lot of swap
> usage :
>
> [root@usnyh-cmd1 ~]# free -m
> totalusedfree shared buff/cache
> available
> Me
Are you sure that swap is used actively? Maybe it had just been used during
backup or something.
Look after SwapIn/SwapOut (si/so) it should be '0'
$ vmstat 1
procs ---memory-- ---swap-- -io -system--
--cpu-
r b swpd free buff cache si sobibo
Hello,
we are running Postgres 10.5 with master slave replication.
These are our custom params
archive_command = 'pgbackrest --stanza=cmdprod archive-push %p' # command
to use to archive a logfile segment
archive_mode = on # enables archiving; off, on, or always
checkpoint_completion_target = 0.7
