pgsql: Refactor confusing code in _mdfd_openseg(). - Mailing list pgsql-committers

From Thomas Munro
Subject pgsql: Refactor confusing code in _mdfd_openseg().
Date
Msg-id E1ivoKi-0001nV-63@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Refactor confusing code in _mdfd_openseg().

As reported independently by a couple of people, _mdfd_openseg() is coded in a
way that seems to imply that the segments could be opened in an order that
isn't strictly sequential.  Even if that were true, it's also using the wrong
comparison.  It's not an active bug, since the condition is always true anyway,
but it's confusing, so replace it with an assertion.

Author: Thomas Munro
Reviewed-by: Andres Freund, Kyotaro Horiguchi, Noah Misch
Discussion: https://postgr.es/m/CA%2BhUKG%2BNBw%2BuSzxF1os-SO6gUuw%3DcqO5DAybk6KnHKzgGvxhxA%40mail.gmail.com
Discussion: https://postgr.es/m/20191222091930.GA1280238%40rfd.leadboat.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f37ff03478aefb5e01d748b85ad86e6213624992

Modified Files
--------------
src/backend/storage/smgr/md.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: In postgres_fdw, don't try to ship MULTIEXPR updates to remote s
Next
From: Tom Lane
Date:
Subject: pgsql: Fix EXPLAIN (SETTINGS) to follow policy about when to print empt