This repository was archived by the owner on May 19, 2020. It is now read-only.
Use Postgres 12 and PostGIS 3.0.0 from upstream #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I also updated the image used in #13 - see here: postgis/docker-postgis#151. So it can be merged as well instead of this one (after the upstream PR is merged). |
It is needed to make ogr2ogr in import-natural-water work with PG 12
eyusupov
force-pushed
the
update-pgsql-and-postgis
branch
from
9714b0c to
c60bac2
Compare
|
This repository has been moved to openmaptiles-tools as See also openmaptiles/openmaptiles-tools#252 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've tested this on the same hardware as openmaptiles/postserve#15
and in the same way (postserve serving tiles and rendering in an openlayers html page) and
it feels much more responsive.
Here are the timings I'm getting:
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/636/316.pbf (172.19.0.1) 199.06ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/637/316.pbf (172.19.0.1) 213.33ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/635/317.pbf (172.19.0.1) 349.40ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/635/316.pbf (172.19.0.1) 394.14ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/636/317.pbf (172.19.0.1) 467.19ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/637/317.pbf (172.19.0.1) 573.53ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/638/316.pbf (172.19.0.1) 39.95ms
[I 191021 15:10:07 web:2246] 304 GET /tiles/10/638/317.pbf (172.19.0.1) 51.17ms
[I 191021 15:12:02 web:2246] 200 GET /tiles/10/639/317.pbf (172.19.0.1) 68.65ms
[I 191021 15:12:05 web:2246] 200 GET /tiles/10/639/318.pbf (172.19.0.1) 99.92ms
[I 191021 15:12:05 web:2246] 200 GET /tiles/10/638/318.pbf (172.19.0.1) 118.73ms
[I 191021 15:12:05 web:2246] 200 GET /tiles/10/636/318.pbf (172.19.0.1) 149.22ms
[I 191021 15:12:05 web:2246] 200 GET /tiles/10/635/318.pbf (172.19.0.1) 101.32ms
[I 191021 15:12:05 web:2246] 200 GET /tiles/10/637/318.pbf (172.19.0.1) 170.65ms
This is
volga_fed_districtarea, and Postgresql is running on an ASUS E520 nettop (Intel(R) Core(TM) i3-7100T CPU @ 3.40GHz, 8 GB Ram) that is running some other stuff as well.In the postserve PR above I was running Postgres 11 with PostGIS 2.5.3.
I didn't do the tests with the current postgis image.