Re: Signed vs. Unsigned (some)
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, ranier.vf@gmail.com
Cc: pgsql-hackers@postgresql.org
Date: 2021-07-02T10:09:23Z
Lists: pgsql-hackers
On 16.06.21 10:48, Peter Eisentraut wrote: > On 15.06.21 10:17, Kyotaro Horiguchi wrote: >> The definitions are not ((type) -1) but ((type) 0xFFFFFFFF) so >> actually they might be different if we forget to widen the constant >> when widening the types. Regarding to the compiler behavior, I think >> we are assuming C99[1] and C99 defines that -1 is converted to >> Uxxx_MAX. (6.3.1.3 Singed and unsigned integers) >> >> I'm +0.2 on it. It might be worthwhile as a matter of style. > > I think since we have the constants we should use them. I have pushed the InvalidBucket changes. The use of InvalidBlockNumber with vac_update_relstats() looks a bit fishy to me. We are using in the same call 0 as the default for num_all_visible_pages, and we generally elsewhere also use 0 as the starting value for relpages, so it's not clear to me why it should be -1 or InvalidBlockNumber here. I'd rather leave it "slightly wrong" for now so it can be checked again.
Commits
-
Silence minor compiler warnings.
- 302612a6c74f 15.0 cited
-
Use InvalidBucket instead of -1 where appropriate
- 6bd3ec62d9d7 15.0 landed
-
Set pg_class.reltuples for partitioned tables
- 0e69f705cc1a 14.0 cited
-
Redefine pg_class.reltuples to be -1 before the first VACUUM or ANALYZE.
- 3d351d916b20 14.0 cited