From: | Jov <amutu(at)amutu(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | wired problem for a 9.1 slave:receive wal but do not replay it? |
Date: | 2014-08-11 10:24:34 |
Message-ID: | CADyrUxO++qaiNAnDG6fnkqm9O_g0fb3gxi4_RVz=HhNBstKg4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Today,our monitor report a pg slave instance'disk space usage reach 96%,I
login in to the machine,and find the pg_xlog dir take up more than
2TB,which is abnormal.
the number of WAL file in the pg_xlog dir is more than 130k,while we set
the wal keep number to 8192.
I think there is something stop the replay,so I check the
pg_stat_activity,pg_prepare_statement,pg_xact etc,but find all normal.
I run:
ps auxwww | grep postgres
and can find the wal receiver and streaming receiver work happily,because
the wal file name,the streaming log id changed.
So I have no idea.
I then restart the slave PG,and find it recover from a very old wal which
is one month ago.
We are now set up a new slave for the master while let the recover from
this slave go.
the PG version is 9.1.9,OS is CentOS 6 x86-64.
Jov
blog: http:amutu.com/blog <http://amutu.com/blog>
From | Date | Subject | |
---|---|---|---|
Next Message | Jen Sing Choe | 2014-08-11 11:33:19 | PgAgent binary distribution for Centos 6.5 |
Previous Message | Rémi Cura | 2014-08-11 10:11:47 | Re: pg_advisory_lock problem |