[openstreetmap/openstreetmap-website] Move GPS tables to a separate database (PR #7111)

[Ruben L. Mendoza]

@Rub21 commented on this pull request.



> @@ -0,0 +1,15 @@
+# frozen_string_literal: true
+
+# Drop the GPS tables (gps_points, gpx_file_tags, gpx_files) from the main database.
+# These tables now live in a separate GPS database (see GpsRecord model).
+class DropGpsTablesFromMainDb < ActiveRecord::Migration[8.1]

Yes, that migration would have deleted trace data,  if anyone deploying this PR. I removed it.

The plan from the ops call is to skip the data copy. Tom suggested reusing the replicas as the new GPS DB. So the steps would be:

- Promote one replica, drop the non-GPS tables, point Rails to it as gps.
- Verify in production.
- Open a new PR with drop migration for the old GPS tables.

For deployers outside OSMF (no replicas), we could add a rake task to copy the GPX data, and also document the migration steps so they can follow the, but  i think that's for another ticket.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7111#discussion_r3326156826
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/7111/review/4391863129 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260529/e402e3f9/attachment.htm>