Postgres database huge after intial import

[tlaugier]

Hi everyone, I just installed a new server and did the initial import for the planet with the address "data style". According to the docs I should be looking at 545 GB of db size but my db is actually 1537 GB!
Is there some cleanup I should be doing after the initial import? I don't think the --drop option is correct for my use case since I plan on doing daily updates on this server.
I'm using the following docker compose file for my server:

version: "3"

services:
    nominatim:
        container_name: nominatim
        image: mediagis/nominatim:4.3
        restart: always
        ports:
            - "127.0.0.1:8080:8080"
            - "5432:5432"
        environment:
            PBF_URL: https://planet.openstreetmap.org/pbf/planet-latest.osm.pbf
            REPLICATION_URL: https://planet.openstreetmap.org/replication/day/
            UPDATE_MODE: "continuous"
            IMPORT_STYLE: "address"
            THREADS: 32
            POSTGRES_MAX_WAL_SIZE: "4GB"
        volumes:
            - type: bind
              source: /data/nominatim/db
              target: /var/lib/postgresql/14/main
            - type: bind
              source: /data/nominatim/nominatim_data
              target: /nominatim
        shm_size: 16gb

[mtmail]

What is the size of the planet_osm_nodes table? Nominatim and https://github.com/mediagis/nominatim-docker/tree/master/4.3#flatnode-files says to use a flatnode file for large imports. For Docker configuration their github repo is more experienced.

[tlaugier]

The planet_osm_nodes table is currently 363 GB.
I did not setup the flatnode files because I was under the impression that it would take event more space for some reason. I will try to add it to my server.

[felix-geovelo]

I'm facing the same problem as @tlaugier, any updates on what we could have done wrong ? ORr what we could do to flush some data and still be able to apply diffs ?

[felix-geovelo]

Thanks for the quick repsonse, I'll try.
But does thoose table (search_name and search_name_XX) are necessary to only use nominatim to feed a photon instance and do updates, can i just drop them ? (I've used --reverse-only param during nominatim initial import)

[lonvia]

Use a flatnode file.

[mtmail]

ah, ok, I thought you had the same setup as @tlaugier

[felix-geovelo]

My bad, I should have specified it.

[tlaugier]

For me using a flat node file was what made me use the less disk space.
With the docker-compose.yml file I posted originally and the added flat node directives, my current database is 925 GB. That's still a lot more than advertised on the various docs but for me that is manageable with my current setup.