| From: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: wal segment failed |
| Date: | 2016-05-18 00:32:04 |
| Message-ID: | CAE_gQfW+Qu2Zs1mj-KQSkqADuKETZJ9NHjC+qOu8mKUhjuJgaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-05-18 00:42:58 | Re: wal segment failed |
| Previous Message | David G. Johnston | 2016-05-18 00:19:44 | Re: wal segment failed |