I'm trying to understand my wals behavior on my postgresql environment.
My wal settings are :

    wal_keep_segments = 200
    max_wal_size = 3GB
    min_wal_size = 80MB
    archive_command = 'cp %p /PostgreSQL-wal/9.6/pg_xlog/wal_archives/%f'
    archive_timeout = 10
    #checkpoint_flush_after = 256kB
    #checkpoint_completion_target = 0.5

My wals directory is /PostgreSQL-wal/9.6/pg_xlog/ and my archives directory
is PostgreSQL-wal/9.6/pg_xlog/wal_archives.
Last night my wals directory storage got full(archive directory also
because they are on the same fs..)l

I have right now 211 wals in my wal`s directory :

    ls -l /PostgreSQL-wal/9.6/pg_xlog/ | wc -l

The only thing that was running during the night are only selects from our
monitoring agent. I guess that wal were created because the archive_timeout
was very low and they were deleted because the wal_keep_segments was high.

This morning , I set the wal_keep_segments to 100 and I set the
archive_timeout to 6 minutes. Now, after setting those settings and
starting the cluster wals switch is working fine and I didnt see that many
wals were created. However, doesnt the old wals should be deleted
automaticly ? Can I delete archives safely ?

Thanks , Mariel.

Reply via email to