问题
Again, I have a function that works fine locally, but moving it online yields a big fat error... Taking a cue from a response in which someone had pointed out the number of arguments I was passing wasn't accurate, I double-checked in this situation to be certain that I am passing 5 arguments to the function itself...
Query failed: ERROR: operator does not exist: point <@> point HINT: No operator matches the given name and argument type(s). You may need to add explicit type casts.
The query is this:
BEGIN; SELECT zip_proximity_sum('zc',
(SELECT g.lat FROM geocoded g
LEFT JOIN masterfile m ON g.recordid = m.id
WHERE m.zip = '10050' ORDER BY m.id LIMIT 1),
(SELECT g.lon FROM geocoded g
LEFT JOIN masterfile m ON g.recordid = m.id
WHERE m.zip = '10050' ORDER BY m.id LIMIT 1),
(SELECT m.zip FROM geocoded g
LEFT JOIN masterfile m ON g.recordid = m.id
WHERE m.zip = '10050' ORDER BY m.id LIMIT 1)
,10);
The PG function is this:
CREATE OR REPLACE FUNCTION zip_proximity_sum(refcursor, numeric, numeric, character, numeric)
RETURNS refcursor AS
$BODY$
BEGIN
OPEN $1 FOR
SELECT r.zip, point($2,$3) <@> point(g.lat, g.lon) AS distance
FROM
geocoded g LEFT JOIN masterfile r ON g.recordid = r.id
WHERE (geo_distance( point($2,$3),point(g.lat,g.lon)) < $5)
ORDER BY r.zip, distance;
RETURN $1;
END;
$BODY$
LANGUAGE 'plpgsql' VOLATILE
COST 100;
回答1:
Here are the exact commands:
create extension cube;
create extension earthdistance;
select (point(-0.1277,51.5073) <@> point(-74.006,40.7144)) as distance;
distance
------------------
3461.10547602474
(1 row)
Note that points are created with LONGITUDE FIRST. Per the documentation:
Points are taken as (longitude, latitude) and not vice versa because longitude is closer to the intuitive idea of x-axis and latitude to y-axis.
Which is terrible design... but that's the way it is.
回答2:
The <@> operator is provided by earthdistance extension.
You need to call create extension earthdistance; on production database.
- More info about Earthdistance: http://www.postgresql.org/docs/9.1/static/earthdistance.html
- Checking available extensions: http://www.postgresql.org/docs/9.1/static/view-pg-available-extensions.html
回答3:
Are you sure that postgis was properly installed on the online server?
回答4:
The point of error is the select statement in your stored procedure:
SELECT r.zip, point($2,$3) <@> point(g.lat, g.lon) AS distance
^
At the marked position an operator is expected, but your operator is either not defined or has other argumet types. Postgres itself only knows of the <@ and @> containment operators. Look here for their explanation.
Can you please elaborate on what you are trying to achieve.
来源:https://stackoverflow.com/questions/2665786/postgres-error-operator-does-not-exist