Re: pgsql: Report which WAL sync method we are trying to change *to* when it

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <mha(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Report which WAL sync method we are trying to change *to* when it
Date: 2008-05-12 19:49:31
Message-ID: 25178.1210621771@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> Magnus seems to say it is possible to set this and then have it fail
> later when it is used. Not sure which is correct.

Per his comment just now, I think he'd gotten confused between
assign_xlog_sync_method (which sets the value) and issue_xlog_fsync
(which uses it).

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2008-05-12 19:59:48 Re: pgsql: Report which WAL sync method we are trying to change *to* when it
Previous Message Magnus Hagander 2008-05-12 19:49:15 Re: pgsql: Report which WAL sync method we are trying to change *to* when it