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

From Tom Lane
Subject Re: Fairly serious bug induced by latest guc enum changes
Date
Msg-id 24537.1210687816@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fairly serious bug induced by latest guc enum changes  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Fairly serious bug induced by latest guc enum changes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> 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...

No, my point was that there are three possible states of sync_bit and
your patch only accounted for transitions between two of 'em.  For
instance, if sync_bit goes to 0 we must close and reopen the file,
else we'll be doing both O_SYNC flush and whatever flush method
is supposed to be getting used.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem returning strings with pgsql 8.3.x
Next
From: "Josh Tolley"
Date:
Subject: Re: Problem returning strings with pgsql 8.3.x