aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-12-24 19:03:21 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2011-12-24 19:03:21 -0500
commit472d3935a2793343e450ba7cda4adbc323a984c3 (patch)
tree30fc6e85cc76a7b48ff84243237ccdc1dd41a00b /src/backend/access/gist/gistbuildbuffers.c
parente2c2c2e8b1df7dfdb01e7e6f6191a569ce3c3195 (diff)
downloadpostgresql-472d3935a2793343e450ba7cda4adbc323a984c3.tar.gz
postgresql-472d3935a2793343e450ba7cda4adbc323a984c3.zip
Rethink representation of index clauses' mapping to index columns.
In commit e2c2c2e8b1df7dfdb01e7e6f6191a569ce3c3195 I made use of nested list structures to show which clauses went with which index columns, but on reflection that's a data structure that only an old-line Lisp hacker could love. Worse, it adds unnecessary complication to the many places that don't much care which clauses go with which index columns. Revert to the previous arrangement of flat lists of clauses, and instead add a parallel integer list of column numbers. The places that care about the pairing can chase both lists with forboth(), while the places that don't care just examine one list the same as before. The only real downside to this is that there are now two more lists that need to be passed to amcostestimate functions in case they care about column matching (which btcostestimate does, so not passing the info is not an option). Rather than deal with 11-argument amcostestimate functions, pass just the IndexPath and expect the functions to extract fields from it. That gets us down to 7 arguments which is better than 11, and it seems more future-proof against likely additions to the information we keep about an index path.
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions