Re: Fairly serious bug induced by latest guc enum changes - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Fairly serious bug induced by latest guc enum changes
Date
Msg-id 20080513155421.7567c530@mha-laptop.hagander.net
Whole thread Raw
In response to Re: Fairly serious bug induced by latest guc enum changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fairly serious bug induced by latest guc enum changes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> I wrote:
> > Okay, but you failed to correctly reproduce the conditions for
> > closing the old file.
> 
> A more bulletproof solution might involve passing sync_method to
> get_sync_bit as an explicit parameter, and then the assign hook
> could do
>     if (get_sync_bit(sync_method) !=
> get_sync_bit(new_sync_method)) XLogFileClose();

Right, but I still need the other part of the check, right? This one
still fails the same check as my patch, no? Because I assume the hole
you found there was that get_sync_bit() will return 0 for two different
sync methods as long as none of them are O_SYNC or O_DSYNC...

//Magnus


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fairly serious bug induced by latest guc enum changes
Next
From: Tom Lane
Date:
Subject: Re: Problem returning strings with pgsql 8.3.x