| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reducing pg_ctl's reaction time |
| Date: | 2017-06-26 20:19:16 |
| Message-ID: | 18520.1498508356@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> The 10 fold increase in log spam during long PITR recoveries is a bit
> unfortunate.
> 9153 2017-06-26 12:55:40.243 PDT FATAL: the database system is starting up
> 9154 2017-06-26 12:55:40.345 PDT FATAL: the database system is starting up
> 9156 2017-06-26 12:55:40.447 PDT FATAL: the database system is starting up
> 9157 2017-06-26 12:55:40.550 PDT FATAL: the database system is starting up
> ...
> I can live with it, but could we use an escalating wait time so it slows
> back down to once a second after a while?
Sure, what do you think an appropriate behavior would be?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-26 20:23:56 | Re: Reducing pg_ctl's reaction time |
| Previous Message | Jeff Janes | 2017-06-26 20:06:44 | Re: Reducing pg_ctl's reaction time |