[Tile-serving] [openstreetmap/osm2pgsql] Store settings to a database table and retrieve for updates (PR #1963)

[Jochen Topf]

> This seems focused on the pgsql backend.

No. This is mostly about the middle and about updates. The idea is that osm2pgsql can tell what parameters to use with updates. We'll have more settings in the future, the replication diff stuff can use this mechanism. And mostly this is preparation for a new middle database scheme. We can use those settings to store which scheme is in use.

> What if someone wants to import into the same DB with multiple prefixes (assuming non-updatable, so no slim tables)

Hm. That is a problem. The only way to fix this I can think of would be to not write the settings table in non-slim mode.

> I view the flat nodes option similar to -d and --middle-schema in that it sets where data is going to be stored. I don't think filesystem paths belong in the DB, as they vary depending on the working directory.

Storing the flat nodes file in the database is important, because this is a problem that comes up every so often. Users want to update a database and forget to mention the flat node file or stuff like that. Storing the file name in the database makes this easier, but the setting can be overridden with a new `--flat-nodes` setting, so you can still move the file if you want to. But there is a problem: Files should be stored as absolute file names so they don't depend on the current working directory. I had planned to do that and forget to implement that.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/pull/1963#issuecomment-1555180326
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/osm2pgsql/pull/1963/c1555180326 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20230519/1e2b2e2c/attachment.htm>