Skip site navigation (1) Skip section navigation (2)

pgsql: Create new routines systable_beginscan_ordered,

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Create new routines systable_beginscan_ordered,
Date: 2008-04-12 23:14:21
Message-ID: (view raw or whole thread)
Lists: pgsql-committers
Log Message:
Create new routines systable_beginscan_ordered, systable_getnext_ordered,
systable_endscan_ordered that have API similar to systable_beginscan etc
(in particular, the passed-in scankeys have heap not index attnums),
but guarantee ordered output, unlike the existing functions.  For the moment
these are just very thin wrappers around index_beginscan/index_getnext/etc.
Someday they might need to get smarter; but for now this is just a code
refactoring exercise to reduce the number of direct callers of index_getnext,
in preparation for changing that function's API.

In passing, remove index_getnext_indexitem, which has been dead code for
quite some time, and will have even less use than that in the presence
of run-time-lossy indexes.

Modified Files:
        tuptoaster.c (r1.85 -> r1.86)
        genam.c (r1.66 -> r1.67)
        indexam.c (r1.105 -> r1.106)
        catalog.c (r1.74 -> r1.75)
        inv_api.c (r1.131 -> r1.132)
        ts_cache.c (r1.6 -> r1.7)
        genam.h (r1.70 -> r1.71)
        relscan.h (r1.62 -> r1.63)
        catalog.h (r1.38 -> r1.39)

pgsql-committers by date

Next:From: Tom LaneDate: 2008-04-12 23:21:04
Subject: pgsql: Clean up a few places where Datums were being treated as pointers
Previous:From: User JbcooleyDate: 2008-04-12 15:52:24
Subject: npgsql - Npgsql2: Test for DataTable.Load and using varchar and char.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group