| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem? |
| Date: | 2014-02-24 23:30:25 |
| Message-ID: | 20140224233025.GC14104@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-24 15:20:13 -0800, Peter Geoghegan wrote:
> On Mon, Feb 24, 2014 at 3:17 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > TBH I don't care about torn pages during normal testing. I don't want to
> > suggest disabling it for real workloads with real data, just that it's
> > important to do so during development/testing of WAL related code,
> > because otherwise it will hide/fixup many errors.
>
> Sure, but you might want to account for torn pages anyway.
> Particularly if you're interested in some degree of automation, as we
> all seem to be.
Hm, well. I have to admit, if a test machine crashes, I'd just rebuild
the cluster. Unless I am working on crash safety testing in which case
I'd probably not have full_page_writes disabled...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2014-02-24 23:44:57 | Re: contrib/cache_scan (Re: What's needed for cache-only table scan?) |
| Previous Message | Peter Geoghegan | 2014-02-24 23:20:13 | Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem? |