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

[Adrien nayrat]

Usually, t is not the application's job to worry about how the RDBMS clean the tables. The default behavior should be "let postgres do the job"  and the "analyze by the application" should be the exception. Not the opposite.

The DBA can control aggressiveness of autovacuum. If you perform analyze or vacuum in the application, how can we control this? I know there are parameters to control that, but this implies to be able to change them.

>From what I can see, new tuples are inserted or deleted. So vacuum is needed to clean old rows or update hint bits. You can only perform COPY FREEZE if "the table being loaded has been created or truncated in the current subtransaction"

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

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