| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Lucas Possamai <drum(dot)lucas(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:19:44 |
| Message-ID: | CAKFQuwbwwt_Oej528uJAZXywHWgmPrjv+YAtOPbTwz6JJPaKgQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, May 17, 2016 at 8:03 PM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>
wrote:
> Failed to archive *WAL* segment `pg_xlog/00000002000011E800000012` on
> host `localhost:30022
>
>
> Guys I'm getting that erro on my master server, and I believe that is
> causing a spike
>
>
> archive command:
>
> archive_command = 'exec nice -n 19 ionice -c 2 -n 7
> ../../bin/archive_command.ssh_to_slaves.bash "%p" prod-db-01 prod-db-02
> localhost:30022'
>
>
>
> Any idea why?
>
If the reason you haven't show the logs of relevant errors from your script
the following will hopefully point you in the right direction.
http://www.postgresql.org/docs/current/static/runtime-config-logging.html#GUC-LOGGING-COLLECTOR
General info on archive_command usage:
http://www.postgresql.org/docs/current/static/continuous-archiving.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lucas Possamai | 2016-05-18 00:32:04 | Re: wal segment failed |
| Previous Message | Lucas Possamai | 2016-05-18 00:03:05 | wal segment failed |