| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Torsten Förtsch <torsten(dot)foertsch(at)gmx(dot)net> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: WAL bandwidth |
| Date: | 2014-05-22 19:52:28 |
| Message-ID: | 20140522195228.GT7857@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Torsten Förtsch wrote:
> That's what I want, to throttle the rate at which WAL is generated by
> maintenance operations.
>
> I take it, there is no such thing by now. Would it be a useful addition?
Uh. See this thread:
http://www.postgresql.org/message-id/CA+U5nMLfxBgHQ1VLSeBHYEMjHXz_OHSkuFdU6_1quiGM0RNKEg@mail.gmail.com
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | basti | 2014-05-23 09:11:54 | archiving transaction log file failed too many times, will try again later |
| Previous Message | John R Pierce | 2014-05-22 19:37:59 | Re: WAL bandwidth |