| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Alexey Klyukin <alexk(at)hintbits(dot)com> |
| Cc: | Adalkonda Harshad <adalkondaharshad(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Standby is not removing restored WAL segments |
| Date: | 2014-09-18 09:01:19 |
| Message-ID: | CAECtzeVvEswxTfauZ=sRn=ET=7BtN2GpRp1hvb0Z4Xof-Pq39A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
2014-09-16 15:03 GMT+02:00 Alexey Klyukin <alexk(at)hintbits(dot)com>:
> On Tue, Sep 16, 2014 at 2:20 PM, Adalkonda Harshad
> <adalkondaharshad(at)gmail(dot)com> wrote:
> >
>
> > I suspect there is a problem while setting the archive_command that
> resulting towards accumulating WAL .ready file in pg_xlog/archive_status
> directory itself.
>
> I think archive_command has no effect on the non-primary server, and
> the problem described above is happening on standby.
> It's hard to suspect the restore_command as well, because the WAL
> segments are copied to the pg_xlog as a result of the restore_command,
> and therefore, it's working.
>
I agree with Alexey. There's nothing wrong with our archive_command. Not
sure what's wrong though.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2014-09-18 09:03:14 | Re: Standby is not removing restored WAL segments |
| Previous Message | Rajiv Kasera | 2014-09-18 04:01:51 | Archiving & Reporting Support in PG9.3 |