On Thu, Mar 03, 2022 at 09:59:03AM +0100, Marc Rechté wrote: > Hello, > > We have a pg_restore which fails due to RAM over-consumption of the > corresponding PG backend, which ends-up with OOM killer. > > The table has one PK, one index, and 3 FK constraints, active while restoring. Send the schema for the table, index, and constraints (\d in psql). What are the server settings ? https://wiki.postgresql.org/wiki/Server_Configuration What OS/version ? > The dump contains over 200M rows for that table and is in custom format, > which corresponds to 37 GB of total relation size in the original DB. > > While importing, one can see the RSS + swap increasing linearly for the > backend (executing the COPY) > > On my machine (quite old PC), it failed after 16 hours, while the disk usage > was reaching 26 GB and memory usage was 9.1g (RSS+swap)
