| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [9.3 bug] disk space in pg_xlog increases during archive recovery |
| Date: | 2014-02-12 12:33:31 |
| Message-ID: | 20140212123331.GG3162@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-12 21:23:54 +0900, MauMau wrote:
> Maybe we could consider in that direction, but there is a problem. Archive
> recovery slows down compared to 9.1, because of repeated restartpoints.
> Archive recovery should be as fast as possible, because it typically applies
> dozens or hundreds of WAL files, and the DBA desires immediate resumption of
> operation.
>
> So, I think we should restore 9.1 behavior for archive recovery.
It's easy to be fast, if it's not correct. I don't see how that
behaviour is acceptable, imo the previous behaviour simply was a bug
whose fix was too invasive to backpatch.
I don't think you can convince me (but maybe others) that the old
behaviour is acceptable.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-02-12 12:52:20 | Re: Recovery inconsistencies, standby much larger than primary |
| Previous Message | MauMau | 2014-02-12 12:28:22 | Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease |