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
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.
=?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
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
=?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
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
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.
> >
> >
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.
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
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
10 matches
Mail list logo