2b95d1cffa
* All functions that access database must be declared as `STABLE`, not `IMMUTABLE` -- because database can change at any moment, e.g. during an update * there are a few functions that could be made `STRICT` -- passing `NULL` as a parameter will always result in a `NULL`, but for some reason that causes a significant decrease in perf. * tagged one function as parallel safe NOTE: somehow `ST_AsMVT()` method of tile generation is showing 70-90% slowdown with this patch. I am not sure of why this is happening. If the reason is the `IMMUTABLE` -> `STABLE` change, we may have to dig deeper into PG optimization
24 lines
652 B
PL/PgSQL
24 lines
652 B
PL/PgSQL
-- etldoc: layer_housenumber[shape=record fillcolor=lightpink, style="rounded,filled",
|
|
-- etldoc: label="layer_housenumber | <z14_> z14+" ] ;
|
|
|
|
CREATE OR REPLACE FUNCTION layer_housenumber(bbox geometry, zoom_level integer)
|
|
RETURNS TABLE
|
|
(
|
|
osm_id bigint,
|
|
geometry geometry,
|
|
housenumber text
|
|
)
|
|
AS
|
|
$$
|
|
SELECT
|
|
-- etldoc: osm_housenumber_point -> layer_housenumber:z14_
|
|
osm_id,
|
|
geometry,
|
|
housenumber
|
|
FROM osm_housenumber_point
|
|
WHERE zoom_level >= 14
|
|
AND geometry && bbox;
|
|
$$ LANGUAGE SQL STABLE
|
|
-- STRICT
|
|
PARALLEL SAFE;
|