BUG #2392: Feature request : point_ops - Mailing list pgsql-bugs

From Raphael Jacquot
Subject BUG #2392: Feature request : point_ops
Date
Msg-id 200604131702.k3DH2wIr051356@wwwmaster.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      2392
Logged by:          Raphael Jacquot
Email address:      raphael.jacquot@imag.fr
PostgreSQL version: 8.1.3
Operating system:   Linux Gentoo 2006.0
Description:        Feature request : point_ops
Details:

I have the following table:

CREATE TABLE gps_points (
    gpx_id            bigint NOT NULL,
    capture_time    timestamp NOT NULL,
    position        point NOT NULL,
    altitude        float,
    CONSTRAINT pk__gps_points PRIMARY KEY (gpx_id, capture_time),
    CONSTRAINT fk__gps_points__gpx_id FOREIGN KEY (gpx_id) REFERENCES
gpx_files(gpx_id)
);

for which I have the following index:
CREATE INDEX i__gps_points__position ON gps_points USING gist
(box(position,position) box_ops);

it would be nice if point_ops would be available so I could write the index
as:

CREATE INDEX i__gps_points__position ON gps_points USING gist (position
point_ops);

and I could then use :

select * from gps_points where position @ box
'((5.6850162,45.278199),(5.7145111,45.307693))';

instead of the current:

select * from gps_points where box(position,position) @ box
'((5.6850162,45.278199),(5.7145111,45.307693))';

pgsql-bugs by date:

Previous
From: "Peter Brant"
Date:
Subject: Re: Permission denied on fsync / Win32 (was right
Next
From: "Alexander Kirpa"
Date:
Subject: BUG #2394: Multiple TRUNCATE within transaction