Mercurial > gemma
view schema/geonames.sql @ 4161:64cd18281c76
Improve performance of row level security policies
Using constraint_column_usage instead of key_column_usage makes
the query twice as fast. I did not explore why. Let's just take it.
Using 'EXISTS(... WHERE ... = value) is often more efficient than
value IN(...) since it allows the inner query to be executed only
up to the point where it turns out to return more than nothing with
filtering directly in place.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Fri, 02 Aug 2019 17:14:13 +0200 |
parents | 2304778c4432 |
children |
line wrap: on
line source
-- This is Free Software under GNU Affero General Public License v >= 3.0 -- without warranty, see README.md and license for details. -- SPDX-License-Identifier: AGPL-3.0-or-later -- License-Filename: LICENSES/AGPL-3.0.txt -- Copyright (C) 2018 by via donau -- – Österreichische Wasserstraßen-Gesellschaft mbH -- Software engineering by Intevation GmbH -- Author(s): -- * Sascha Wilde <wilde@intevation.de> -- Tables for data from geonames database -- https://download.geonames.org/ -- used for searching cities and villages... CREATE TABLE waterway.geonames ( geonameid int PRIMARY KEY, name varchar(200) NOT NULL, asciiname varchar(200), alternatenames varchar(10000), location geography(POINT, 4326) NOT NULL, feature_class char(1), feature_code varchar(10), country_code char(2), cc2 varchar(200), admin1_code varchar(20), admin2_code varchar(80), admin3_code varchar(20), admin4_code varchar(20), population int, elevation int, dem int, timezone varchar(40), modification_date timestamp );