[openstreetmap/openstreetmap-website] Move GPS tables to a separate database (PR #7111)
Paul Norman
notifications at github.com
Fri May 29 11:35:14 UTC 2026
pnorman left a comment (openstreetmap/openstreetmap-website#7111)
> In general I'm neutral on this idea. I've read the operations task and I haven't seen convincing evidence that this is the best way to solve the operational problems
We discussed splitting the DBs on the ops call and talked about moving the traces to the old DB servers. The only other gain from splitting would be that we could have different cluster-level settings and WAL/basebackup
It doesn't add anything new to pg_dump since that can already exclude tables.
Personally I'm not convinced this is the biggest trace problem. The API results in ORDER BY ... OFFSET ... queries which are horrible for performance.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7111#issuecomment-4574447359
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/pull/7111/c4574447359 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260529/b563ae7a/attachment.htm>
More information about the rails-dev
mailing list