On Sun, Feb 26, 2017, 13:15 Marcell Ribeiro <[email protected]>
wrote:

> O meu wal_keep_segments tava 100 e eu mudei pra 10 com o servidor em
> execução, o pg_xlog diminuiu de 109 GB pra 50 GB. Isso pode dar algum
> problema no banco?
>

o wal_keep_segments é usado para replicação¹, ele define quantos últimos
wals serão preservados para que se o standby server estiver atrasado possa
se atualizar e seguir o master, se voce não utilizar replicação, pode zerar
esse valor.


1-
https://www.postgresql.org/docs/current/static/runtime-config-replication.html



> Em 26 de fevereiro de 2017 12:00, Marcell Ribeiro <
> [email protected]> escreveu:
>
> Segue o retorno dos selects, Euler:
>
> select name, setting from pg_settings where name ~
> 'checkpoint|wal|version';
>
>              name             |   setting
> ------------------------------+-------------
>  checkpoint_completion_target | 0.3
>  checkpoint_segments              | 10
>  checkpoint_timeout                  | 300
>  checkpoint_warning                 | 30
>  log_checkpoints                       | off
>  max_wal_senders                    | 5
>  server_version                          | 9.3.5
>  server_version_num                 | 90305
>  wal_block_size                         | 8192
>  wal_buffers                               | 2048
>  wal_keep_segments                 | 10
>  wal_level                                   | hot_standby
>  wal_receiver_status_interval     | 10
>  wal_receiver_timeout                | 60000
>  wal_segment_size                    | 2048
>  wal_sender_timeout                  | 60000
>  wal_sync_method                     | fsync
>  wal_writer_delay                       | 200
>
> ---------------------------------------------------
>
> select pg_xlogfile_name(pg_current_xlog_location());
>
>      pg_xlogfile_name
> --------------------------
>  00000001000001E400000057
>
> ---------------------------------------------------
>
> select pg_ls_dir('pg_xlog');
>
>         pg_ls_dir
> --------------------------
>  archive_status
>  00000001000001E400000058
>  00000001000001E400000059
>  00000001000001E40000005A
>  00000001000001E40000005B
>  00000001000001E40000005C
>  00000001000001E40000005D
>  00000001000001E40000006C
>  00000001000001E400000055
>  00000001000001E40000005E
>  00000001000001E40000005F
>  00000001000001E400000060
>  00000001000001E400000061
>  00000001000001E400000062
>  00000001000001E400000063
>  00000001000001E400000064
>  00000001000001E400000065
>  00000001000001E400000066
>  00000001000001E400000067
>  00000001000001E400000068
>  00000001000001E400000069
>  00000001000001E40000006A
>  00000001000001E40000006B
>  00000001000001E40000004D
>  00000001000001E40000004E
>  00000001000001E40000004F
>  00000001000001E400000050
>  00000001000001E400000051
>  00000001000001E400000052
>  00000001000001E400000053
>  00000001000001E400000054
>  00000001000001E400000056
>  00000001000001E400000057
>
> ---------------------------------------------------
>
>
>
>
>
> Em 25 de fevereiro de 2017 21:20, Euler Taveira <[email protected]>
> escreveu:
>
> On 25-02-2017 18:33, Marcell Ribeiro wrote:
> > Boa noite galera. Meu pg_xlog está gigante mesmo com meu archive_command
> > funcionando. Nos logs não tem nenhum erro acontecendo. O que posso fazer
> > pra diminuir esse pg_xlog com segurança?
> >
> Falta informação... Qual a saída das seguintes consultas?
>
> select name, setting from pg_settings where name ~
> 'checkpoint|wal|version';
> select pg_xlogfile_name(pg_current_xlog_location());
> select pg_ls_dir('pg_xlog');
> select * from pg_stat_archiver; -- se >= 9.4
> select * from pg_replication_slots; -- se >= 9.5
>
>
> --
>    Euler Taveira                   Timbira - http://www.timbira.com.br/
>    PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
> _______________________________________________
> pgbr-geral mailing list
> [email protected]
> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
>
>
>
>
> --
>
>
> [image: --]
>
> Marcell Ribeiro
> [image: https://]about.me/marcellribeiro
>
> <https://about.me/marcellribeiro?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links>
>
>
>
>
> --
>
>
> [image: --]
>
> Marcell Ribeiro
> [image: https://]about.me/marcellribeiro
>
> <https://about.me/marcellribeiro?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links>
> _______________________________________________
> pgbr-geral mailing list
> [email protected]
> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral

-- 
Douglas Paulo Ghirelli
Profissional de Tecnologia da Informação
_______________________________________________
pgbr-geral mailing list
[email protected]
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral

Responder a