| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Ludovic Vaugeois-Pepin <ludovicvp(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: wal_retrieve_retry_interval |
| Date: | 2017-10-17 04:54:54 |
| Message-ID: | CAB7nPqQsDR3oxnmeKpoTkT1uZKKqzNXFX_h=LZkOsO2ZhXyztg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 29, 2017 at 3:58 PM, Ludovic Vaugeois-Pepin
<ludovicvp(at)gmail(dot)com> wrote:
> < 2017-05-29 22:42:17.026 CEST > DEBUG: switched WAL source from
> archive to stream after failure
> ... (15 seconds later) ...
> < 2017-05-29 22:42:32.042 CEST > DEBUG: switched WAL source from
> stream to archive after failure
Ludovic, is there some event happening between those two logs?
Something that could explain a longer delay is the time it takes for a
WAL receiver to be considered as started (see WALRCV_STARTUP_TIMEOUT).
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Feike Steenbergen | 2017-10-17 06:01:02 | Re: Making subscribers read only in Postgres 10 logical replication |
| Previous Message | Michael Paquier | 2017-10-17 01:18:21 | Re: could not fdatasync log file: Input/output error |