Re: wal segment failed
| От | Lucas Possamai |
|---|---|
| Тема | Re: wal segment failed |
| Дата | |
| Msg-id | CAE_gQfW+Qu2Zs1mj-KQSkqADuKETZJ9NHjC+qOu8mKUhjuJgaQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: wal segment failed ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: wal segment failed
|
| Список | pgsql-admin |
yep so..
1 master and 2 slaves
all of those server are working..
The only error I got is this one:
Failed to archive WAL segment `pg_xlog/00000002000011E800000012` on host `localhost:30022
I'm having spikes that cause me outage every 15 minutes.. I believe the cause of those spikes is that error above.
The server was rebooted and a parameter on postgres.conf was changed:
shared_buffer.
So i don't believe the cause of this is that change.
Before the reboot on the server, everything was working.
I just can't find the solution.
What I did:
1 - I can connect via postgres user between all the servers
2 - the file 00000002000011E800000012 is into the master /pg_xlog (it was already there)
2 - the file 00000002000011E800000012 is into the slaves server /9.2/data/wal_archive (it was already there)
В списке pgsql-admin по дате отправления: