[Tile-serving] [osm2pgsql-dev/osm2pgsql] osm2pgsql should not perform analyze by itself (Issue #2094)

[Jochen Topf]

I have seen the same issues in logs, too. Interestingly enough I came to the opposite conclusion: Maybe we have to do the `VACUUM` ourselves also instead of relying on the autovacuum to do its jobs whenever it feels like doing so. The problem from my experience is that working with a table that has not been analyzed can mean PostgreSQL will choose a disastrous plan and that's something we can not risk. I know that eventually PostgreSQL will probably get around to doing the ANALYZE  automatically, but "eventually" is not something I can work with.

And there is another issue behind this. Why is the vacuum even necessary? We created that table and we fill it with COPY. If I understand the docs correctly, we should be able to do a `COPY FREEZE` which means we don't need the vacuum, doesn't it? Currently we can not do this easily because of the way the code is structured (table creation and copy is run in different threads), but maybe this would be a better solution.

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

Message ID: <osm2pgsql-dev/osm2pgsql/issues/2094/1764347781 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20231016/646f1302/attachment.htm>