RE: Replication: slave server has 3x size of production server?

________________________________

De: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Enviado: sábado, 22 de fevereiro de 2020 14:33
Para: Edson Richter <edsonrichter(at)hotmail(dot)com>; pgsql-general <pgsql-general(at)postgresql(dot)org>
Assunto: Re: Replication: slave server has 3x size of production server?

On 2/22/20 9:25 AM, Edson Richter wrote:
> Hi!
>
> I've a database cluster created at 9.6.10 linux x64 server rhel. I made
> progressive upgrades, first upgrading slave and then upgrading master.
> Actually both are running 9.6.17.
> Current production server has 196Gb in size.
> Nevertheless, the replicated (slave) server has 598 Gb in size.
> Replication server has 3x size of production server, is that normal?

How are you measuring the sizes?

This is the command:

du --max-depth 1 -h pgDbCluster

Production:

du --max-depth 1 -h pgDbCluster

56M pgDbCluster/pg_log
444K pgDbCluster/global
4,0K pgDbCluster/pg_stat
4,0K pgDbCluster/pg_snapshots
16K pgDbCluster/pg_logical
20K pgDbCluster/pg_replslot
61M pgDbCluster/pg_subtrans
4,0K pgDbCluster/pg_commit_ts
465M pgDbCluster/pg_xlog
4,0K pgDbCluster/pg_twophase
12M pgDbCluster/pg_multixact
4,0K pgDbCluster/pg_serial
195G pgDbCluster/base
284K pgDbCluster/pg_stat_tmp
12M pgDbCluster/pg_clog
4,0K pgDbCluster/pg_dynshmem
12K pgDbCluster/pg_notify
4,0K pgDbCluster/pg_tblspc
196G pgDbCluster

Slave:

du -h --max-depth 1 pgDbCluster

403G pgDbCluster/pg_xlog
120K pgDbCluster/pg_log
424K pgDbCluster/global
0 pgDbCluster/pg_stat
0 pgDbCluster/pg_snapshots
4,0K pgDbCluster/pg_logical
8,0K pgDbCluster/pg_replslot
60M pgDbCluster/pg_subtrans
0 pgDbCluster/pg_commit_ts
0 pgDbCluster/pg_twophase
11M pgDbCluster/pg_multixact
0 pgDbCluster/pg_serial
195G pgDbCluster/base
12M pgDbCluster/pg_clog
0 pgDbCluster/pg_dynshmem
8,0K pgDbCluster/pg_notify
12K pgDbCluster/pg_stat_tmp
0 pgDbCluster/pg_tblspc
598G pgDbCluster

Edson

Where is the space being taken up on disk?

>
> Shall I drop the slave server and re-create it? How to avoid this
> situation in future?
>
> Thanks,
>
> Edson
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com