Re: [HACKERS] R-Tree operators

2004-09-17 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > I'm starting to get a better idea of what's going on here though. Is it the > case that the operators in the operator class are only used when actually > doing an index scan? Not even that, really. The operator class is what the planner uses to detect that

Re: [HACKERS] R-Tree operators

2004-09-17 Thread Greg Stark
Tom Lane <[EMAIL PROTECTED]> writes: > Greg Stark <[EMAIL PROTECTED]> writes: > > I don't understand what overlap_{left,right} are supposed to mean. > > In this thread: > http://archives.postgresql.org/pgsql-general/2004-03/msg01135.php > we had decided that the rtree stuff is not only poorly do

Re: [HACKERS] R-Tree operators

2004-09-17 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > I don't understand what overlap_{left,right} are supposed to mean. In this thread: http://archives.postgresql.org/pgsql-general/2004-03/msg01135.php we had decided that the rtree stuff is not only poorly documented but actively broken. I had thought that B

[HACKERS] R-Tree operators

2004-09-17 Thread Greg Stark
I don't understand what overlap_{left,right} are supposed to mean. In general what seems to be missing from the documentation of operator strategies and support functions is what invariants between them are required. Can I just make up a meaning for overlap_{left,right}? That's what other r-tree