Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ. - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ.
Date
Msg-id 4E16B037020000250003F0DA@gw.wicourts.gov
Whole thread Raw
Responses Re: Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ.  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas  wrote:
> I'm getting a bunch of warnings on Windows related to this:
>> .\src\backend\storage\lmgr\predicate.c(768): warning C4307: '+' :
>>    integral constant overflow
The part of the expression which is probably causing this: (MaxTransactionId + 1) / OLDSERXID_ENTRIESPERPAGE - 1
Which I fear may not be getting into overflow which will not do the
right thing even where there is no warning.  :-(
Would it be safe to assume that integer division would do the right
thing if we drop both of the "off by one" adjustments and use?: MaxTransactionId / OLDSERXID_ENTRIESPERPAGE
-Kevin


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Latch implementation that wakes on postmaster death on both win32 and Unix
Next
From: Heikki Linnakangas
Date:
Subject: Re: Latch implementation that wakes on postmaster death on both win32 and Unix