diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-01-14 22:03:35 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-01-14 22:03:35 +0000 |
| commit | f7ea9312877abcb508669359fa2a05fc69ec91b9 (patch) | |
| tree | 5091d2d5bf06da0955d86c20038f9fa7eaf48346 /src/backend/access/gist/gistxlog.c | |
| parent | 7930e627d8aaf617f4edb8b9e4fe410cc475a93a (diff) | |
| download | postgresql-f7ea9312877abcb508669359fa2a05fc69ec91b9.tar.gz postgresql-f7ea9312877abcb508669359fa2a05fc69ec91b9.zip | |
Some minor code cleanup, falling out from the removal of rtree. SK_NEGATE
isn't being used anywhere anymore, and there seems no point in a generic
index_keytest() routine when two out of three remaining access methods
aren't using it. Also, add a comment documenting a convention for
letting access methods define private flag bits in ScanKey sk_flags.
There are no such flags at the moment but I'm thinking about changing
btree's handling of "required keys" to use flag bits in the keys
rather than a count of required key positions. Also, if some AM did
still want SK_NEGATE then it would be reasonable to treat it as a private
flag bit.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions