Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Hackers > Re: Fairly seri...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 11 of 17 Topic 9348 of 11013
Post > Topic >>

Re: Fairly serious bug induced by latest guc enum changes

by magnus@[EMAIL PROTECTED] (Magnus Hagander) Jul 1, 2008 at 08:06 PM

Tom Lane wrote:
> Bruce Momjian <bruce@[EMAIL PROTECTED]
> writes:
>> Tom Lane wrote:
>>> No, my point was that there are three possible states of sync_bit and
>>> your patch only accounted for transitions between two of 'em.
> 
>> Did this every get addressed?  I don't see a commit for it.
> 
> I thought it got fixed here:
> 
> 2008-05-14 10:02  mha
> 
> 	* src/backend/access/transam/xlog.c: Remove the special variable
> 	for open_sync_bit used in O_SYNC and O_DSYNC modes, replacing it
> 	with a call to a function that derives it from the sync_method
> 	variable, now that it has distinct values for these two cases.
> 	
> 	This means that assign_xlog_sync_method() no longer changes any
> 	settings, thus fixing the bug introduced in the change to use a guc
> 	enum for wal_sync_method.
> 
> Hmm ... or at least more or less fixed.  Seems like there's no provision
> to close and reopen the file if enableFsync changes.  Not sure if that's
> worth worrying about.

We didn't have that before either, did we? We close it when the sync bit
changes, but not just if we change say between fsync() and fdatasync().
Is there any actual reason we'd want to close it?

//Magnus

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
 




 17 Posts in Topic:
Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-05-12 16:22:12 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-05-12 22:33:33 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-05-12 18:46:06 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-05-13 08:07:02 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-05-13 09:44:14 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-05-13 09:50:29 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-05-13 15:54:21 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-05-13 10:10:16 
Re: Fairly serious bug induced by latest guc enum
bruce@[EMAIL PROTECTED]   2008-06-30 16:29:48 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-06-30 16:41:12 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-07-01 20:06:00 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-07-01 14:51:21 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-07-01 20:57:38 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-07-01 15:07:21 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-07-01 21:10:34 
Re: Fairly serious bug induced by latest guc enum changes
tgl@[EMAIL PROTECTED] (T  2008-07-01 15:17:06 
Re: Fairly serious bug induced by latest guc enum changes
magnus@[EMAIL PROTECTED]   2008-07-02 14:11:21 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Dec 5 9:03:57 CST 2008.