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.
Thi
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 con
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
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 co
On Tue, 2020-05-05 at 07:56 +0200, Marc Rechté wrote:
Thanks for answers. Further readings make me think that we should *not*
start postgres with numactl --interleave=all: this may have counter
productive effect on backends anon memory (heap, stack). IMHO, what is
important is to use Huge Pages
Hi,
On 2020-04-29 10:50:54 +0200, Laurenz Albe wrote:
On Wed, 2020-04-29 at 08:54 +0200, Marc Rechté wrote:
I am trying to figure out the recommended settings for a PG dedicated
machine regarding NUMA.
I assume that the shared buffers are using Huge Phages only. Please
correct if I am wrong
Hello,
I am trying to figure out the recommended settings for a PG dedicated
machine regarding NUMA.
I assume that the shared buffers are using Huge Phages only. Please
correct if I am wrong:
1) postgres is started with numactl --interleave=all, in order to spread
memory pages evenly on no
