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 20:34
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 2:51 PM, Edson Richter wrote:

>
> Yes, it is working. Last X'log file is present on all thee servers.
> Also, comparting last transaction number on master and slave shows that
> all are in sync.
> Last, but not least, select max(id) from a busy table shows same id
> (when queried almost simultaneously using a simple test routine).

Well something is keeping those WAL file around. You probably should
analyze your complete setup to see what else is touching those servers.

It is safe to add a "--remove-source-files" into my archive_command as folows into my slave server?

archive_command = 'rsync --remove-source-files -e "ssh -2 -C -p 2022" -az %p barman(at)192(dot)168(dot)0(dot)2:/dados/barman/dbcluster/incoming/%f'

and remove the xlog file after copy to barman?
I mean, whem the archive command starts, the wal has been already processed by the slave server, so we don't need them after copying to backup server, right?

Regards,

Edson

>
> >
> >
> > The files are about 7 months old.
>
> Are there newer files that would indicate that the streaming is working?
>
>
> Yes, streaming is working properly (as stated above).
>
> Thanks,
>
>
> Edson Richter
>
>
>>

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