Re: OOM killer while pg_restore

2022-03-05 Thread Ranier Vilela
Em qui., 3 de mar. de 2022 às 15:32, Marc Rechté escreveu: > Le 03/03/2022 à 16:31, Tom Lane a écrit : > > =?UTF-8?Q?Marc_Recht=c3=a9?= writes: > >> 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

Re: OOM killer while pg_restore

2022-03-05 Thread Marc Rechté
Le 03/03/2022 à 19:43, Tom Lane a écrit : =?UTF-8?Q?Marc_Recht=c3=a9?= writes: Le 03/03/2022 à 16:31, Tom Lane a écrit : Does memory consumption hold steady if you drop the FK constraints? Actually the number of rows is 232735712. Accordingly the RAM consumption would be x12 x3 = 7.8 GiB.

Re: OOM killer while pg_restore

2022-03-03 Thread Tom Lane
=?UTF-8?Q?Marc_Recht=c3=a9?= writes: > Le 03/03/2022 à 16:31, Tom Lane a écrit : >> Does memory consumption hold steady if you drop the FK constraints? > Actually the number of rows is 232735712. > Accordingly the RAM consumption would be x12 x3 = 7.8 GiB. > This is close to the 8,1g I reported

Re: OOM killer while pg_restore

2022-03-03 Thread Marc Rechté
Le 03/03/2022 à 16:31, Tom Lane a écrit : =?UTF-8?Q?Marc_Recht=c3=a9?= writes: 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. The dump

Re: OOM killer while pg_restore

2022-03-03 Thread Tom Lane
=?UTF-8?Q?Marc_Recht=c3=a9?= writes: > 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. > The dump contains over 200M rows for that

Re: OOM killer while pg_restore

2022-03-03 Thread Justin Pryzby
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

Re: OOM killer while pg_restore

2022-03-03 Thread Ranier Vilela
Em qui., 3 de mar. de 2022 às 09:19, Marc Rechté escreveu: > Em qui., 3 de mar. de 2022 às 05:59, Marc Rechté > escreveu: > > > > Hello, > > > > We have a pg_restore which fails due to RAM over-consumption of > > the corresponding PG backend, which ends-up with OOM killer. > > > >

Re: OOM killer while pg_restore

2022-03-03 Thread Marc Rechté
Em qui., 3 de mar. de 2022 às 05:59, Marc Rechté escreveu: 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.

Re: OOM killer while pg_restore

2022-03-03 Thread Ranier Vilela
Em qui., 3 de mar. de 2022 às 05:59, Marc Rechté escreveu: > 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. > The dump

OOM killer while pg_restore

2022-03-03 Thread Marc Rechté
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. The dump contains over 200M rows for that table and is in custom format, which