You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: lonvia [Submitted to the original trac issue database at 4.40pm, Saturday, 22nd May 2010]
I'm running a DB with a full planet using osmosis simple psql schema
and updating it once a day. That worked fine most of the time but
occasionally I had the problem that the daily update took significantly
longer (8 hours instead of the usual 3h). Postgresql was stuck in a 'delete relation' request for hours using 100% CPU and reading a lot of data from the disc.
I searched around a bit and noticed that there is no index on the relation_id column in the relation_members table. The creation of the index seems to have been forgotten in the table creation script pgsql_simple_schema_0.6.sql. If psql is doing a sequential scan of that table for every deleted relation, that would certainly explain the symptoms I have seen.
The text was updated successfully, but these errors were encountered:
Reporter: lonvia
[Submitted to the original trac issue database at 4.40pm, Saturday, 22nd May 2010]
I'm running a DB with a full planet using osmosis simple psql schema
and updating it once a day. That worked fine most of the time but
occasionally I had the problem that the daily update took significantly
longer (8 hours instead of the usual 3h). Postgresql was stuck in a 'delete relation' request for hours using 100% CPU and reading a lot of data from the disc.
I searched around a bit and noticed that there is no index on the relation_id column in the relation_members table. The creation of the index seems to have been forgotten in the table creation script pgsql_simple_schema_0.6.sql. If psql is doing a sequential scan of that table for every deleted relation, that would certainly explain the symptoms I have seen.
The text was updated successfully, but these errors were encountered: