Обсуждение: [GENERAL] streaming replication and archive_status

Hi All,

anyone knows why there are so many files in the directory pg_xlog/archive_status/ in replication server?

# pg_xlog/archive_status/ | wc -l

75217

Is possible to clean this .done files or just don't need to worry ?

It's not occurs on primary or standalone servers, just on replication.

On Mon, Apr 17, 2017 at 12:22 PM, Luciano Mittmann <mittmann@gmail.com> wrote:

Hi All,

anyone knows why there are so many files in the directory pg_xlog/archive_status/ in replication server? 

# pg_xlog/archive_status/ | wc -l

75217

Is possible to clean this .done files or just don't need to worry ?

It's not occurs on primary or standalone servers, just on replication.

What version?  Are you logging checkpoints, and if so what do they say?

Hi Jeff,

checkpoint message on standby node:

[ 2017-04-17 17:21:56 BRT] @ LOG:  restartpoint complete: wrote 21475 buffers (2.6%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=149.816 s, sync=0.064 s, total=149.890 s; sync files=314, longest=0.002 s, average=0.000 s; distance=145449 kB, estimate=236346 kB
[ 2017-04-17 17:21:56 BRT] @ LOG:  recovery restart point at 126/A7072A88
[ 2017-04-17 17:21:56 BRT] @ DETAIL:  last completed transaction was at log time 2017-04-17 17:21:02.289164-03

2017-04-17 17:08 GMT-03:00 Jeff Janes <jeff.janes@gmail.com>:

On Mon, Apr 17, 2017 at 12:22 PM, Luciano Mittmann <mittmann@gmail.com> wrote:

Hi All,

anyone knows why there are so many files in the directory pg_xlog/archive_status/ in replication server? 

# pg_xlog/archive_status/ | wc -l

75217

Is possible to clean this .done files or just don't need to worry ?

It's not occurs on primary or standalone servers, just on replication.

What version?  Are you logging checkpoints, and if so what do they say?

On Mon, Apr 17, 2017 at 1:24 PM, Luciano Mittmann <mittmann@gmail.com> wrote:

Hi Jeff,

checkpoint message on standby node:

[ 2017-04-17 17:21:56 BRT] @ LOG:  restartpoint complete: wrote 21475 buffers (2.6%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=149.816 s, sync=0.064 s, total=149.890 s; sync files=314, longest=0.002 s, average=0.000 s; distance=145449 kB, estimate=236346 kB
[ 2017-04-17 17:21:56 BRT] @ LOG:  recovery restart point at 126/A7072A88
[ 2017-04-17 17:21:56 BRT] @ DETAIL:  last completed transaction was at log time 2017-04-17 17:21:02.289164-03

Gostaria que o código de log de ponto de verificação lhe dissesse quantos arquivos de log de transações ele intencionalmente mantidos também. Eu não vi "acidentalmente" reter arquivos, mas vendo o número registrado ajudaria a simplificar a solução de problemas.

Does each file in pg_xlog/archive_status/ have a corresponding file one directory up?

Cheers,

Jeff

Hi Jeff,

**Does each file in pg_xlog/archive_status/ have a corresponding file one directory up?

no corresponding file on pg_xlog directory. That is the question.. for
some reason or some parameter that I do not know, the files are considered consumed but are not erased later.

On Tue, Apr 18, 2017 at 5:20 AM, Luciano Mittmann <mittmann@gmail.com> wrote:

Hi Jeff,

**Does each file in pg_xlog/archive_status/ have a corresponding file one directory up?

no corresponding file on pg_xlog directory. That is the question.. for
some reason or some parameter that I do not know, the files are considered consumed but are not erased later.

I can see how a well-timed crash could leave behind a few .done files, but not 75 thousand of them.

Are they still accumulating, or was it only an historical accumulation?

 

Also, is this on Windows?

Cheers,

Jeff