| 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:17:40 |
| Message-ID: | 20140224231740.GA11965@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-24 15:05:37 -0800, Peter Geoghegan wrote:
> On Mon, Feb 24, 2014 at 1:17 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > We somehow need to have a policy of testing changes to the WAL format
> > without full_page_writes. They hide bugs in replay far, far too often.
>
> What's the easiest way to get atomic page writes at the FS level on
> your laptop? ZFS or some data journaling FS, I suppose.
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.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-02-24 23:20:13 | Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem? |
| Previous Message | Andres Freund | 2014-02-24 23:16:05 | Re: Changeset Extraction v7.7 |