pgsql: Cosmetic cleanup of ginInsertValue().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Cosmetic cleanup of ginInsertValue().
Date: 2012-07-13 15:37:48
Message-ID: E1SphwC-0002vF-32@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Cosmetic cleanup of ginInsertValue().

Make it clearer that the passed stack mustn't be empty, and that we
are not supposed to fall off the end of the stack in the main loop.
Tighten the loop that extracts the root block number, too.

Markus Wanner and Tom Lane

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/1a9405d26537c6d95269bf48f5ea80fbf7967260

Modified Files
--------------
src/backend/access/gin/ginbtree.c | 20 +++++++++++---------
1 files changed, 11 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-07-13 21:17:10 pgsql: Add fsync capability to initdb, and use sync_file_range() if ava
Previous Message Jan Urbański 2012-07-13 11:38:07 Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.