[Tile-serving] [osm2pgsql-dev/osm2pgsql] Refuse to import data when there is an osm2pgsql_properties table (PR #2085)

[Jochen Topf]

@rustprooflabs As the moment there is no `--force` option or something like that but you have to either drop the database and create a new one or delete the `osm2pgsql_properties` table. But that's certainly something we could think about. I am worried though that people will just get into the habit of using `--force` and then it didn't buy us much. What do you think?

I realize that this is quite a change compared to earlier behaviour, so maybe it is the wrong move here. I created this because I have been bitten twice already with this recently. The reason this is a bit more of a problem now than it was before is the `osm2pgsql_replication` table. It is created first thing in the database, even before, for instance, the input file is opened. So it is easy to clobber that table with an invalid osm2pgsql command line.

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

Message ID: <osm2pgsql-dev/osm2pgsql/pull/2085/c1732652376 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20230924/64a50962/attachment-0001.htm>