Re: Replication: slave server has 3x size of production server?
От | Adrian Klaver |
---|---|
Тема | Re: Replication: slave server has 3x size of production server? |
Дата | |
Msg-id | 590174e0-256a-fe72-468a-0bcf77ca0df8@aklaver.com обсуждение исходный текст |
Ответ на | RE: Replication: slave server has 3x size of production server? (Edson Richter <edsonrichter@hotmail.com>) |
Ответы |
RE: Replication: slave server has 3x size of production server?
|
Список | pgsql-general |
On 2/22/20 10:05 AM, Edson Richter wrote: > ------------------------------------------------------------------------ > > *De:* Adrian Klaver <adrian.klaver@aklaver.com> > *Enviado:* sábado, 22 de fevereiro de 2020 14:33 > *Para:* Edson Richter <edsonrichter@hotmail.com>; pgsql-general > <pgsql-general@postgresql.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 So the WAL logs are not being cleared. What replication method is being used? What are the settings for the replication? > > > Edson > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: