Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldbkR-000659-NQ for pgsql-docs@arkaria.postgresql.org; Mon, 03 May 2021 16:48:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ldbkQ-0002rl-G0 for pgsql-docs@arkaria.postgresql.org; Mon, 03 May 2021 16:48:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldbkQ-0002rd-7t for pgsql-docs@lists.postgresql.org; Mon, 03 May 2021 16:48:42 +0000 Received: from mail-wr1-x42e.google.com ([2a00:1450:4864:20::42e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ldbkI-0000w8-RB for pgsql-docs@lists.postgresql.org; Mon, 03 May 2021 16:48:41 +0000 Received: by mail-wr1-x42e.google.com with SMTP id x7so6288659wrw.10 for ; Mon, 03 May 2021 09:48:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=HjKKWw0QOfkAQgr10vHGXHskbciUqXJdyIJeBHUlos4=; b=It3gmm4jRGg9Pq3WHH+BblOcVFe3VgmSF4YoS6cxaS+Kh4G08nfobZXZpqJVnOwYGE Tts1CAF/CZJmGHQjocjqcNefuqTO11xdp4eaVrKGaZO69Iznqy48sX+rGqfCopReVXfh 9D1Q0jME8QhAWDMOpHi2QHHuxxridhuCyk7zuTLDc1inrVwxBESVR4eIz/2rMyEuqtli 2M+Yu4BD5a7276WRmopxpcwfVANZQUA+1DZP05um5sdDWUW8qnRHcgRD9rKsT1202GnM 1X8CPDc/rpIm2OlE7dJEmml2K5V3owW4G2/lXyAK0hE34uoHSCVCYb3bffGeVQCTGJ0t 8wBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=HjKKWw0QOfkAQgr10vHGXHskbciUqXJdyIJeBHUlos4=; b=SMBYaSCbqWBFL1NI+msRNFQKCm6UTOD3z2XQU1nmpkK/sSVBuR9LbCXQTB+JMoFkaj 0h+0p2BZ32kxhgudFMyyL5C/9vi18jc8XWKQAzEV7+toJxmwz3w/ExSMRQU6mbWP4mxn 06iaf5YpKB5UjhNnrjFfZhMSZVaasOq9UHC9MubpDKILvtvMmDHFMpKDN6LkGOk4/eQ8 eBVr/vqMqsAPEmTfqDirftEihlt/Xugu1P/1YsAzrTUGS/fCMHNP3NT/A1gMei7BU3DX OGPw2rqn9UciADC4KbJVgl47fQpjAumR0uCNPbxLO2F9CmEI/21fSY0rl8lcbtyusARG uSkA== X-Gm-Message-State: AOAM5313bFeLU8vhLZuyGZ3xZWrFzOBIwYQ0zu9eFt5d+IcZ5pDqPG6O SOPLzgSb+LjqeA56MmDWqDxLtdOo3fXrU7jjCyeQ66Vik4U= X-Google-Smtp-Source: ABdhPJwjQzXD8t2wlaf7ZWILsr5b7GrV+Yv+BKD/A3Jp1UXUbA4tKMZ6mg6CtoXHRpBzqlS7dAh7Xy8Htyg61T4g3Dw= X-Received: by 2002:a5d:638f:: with SMTP id p15mr26276210wru.255.1620060513480; Mon, 03 May 2021 09:48:33 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= Date: Mon, 3 May 2021 13:48:21 -0300 Message-ID: Subject: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM To: pgsql-docs@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, There's a well known limitation in the amount of memory that any VACUUM process can use, capped at 1GB now. This is not reflected in the documentation https://www.postgresql.org/docs/current/runtime-config-resource.html We should add a line that indicates that there is a limitation (that should be IMO, backported to documentation of earlier versions as it affects all supported versions), at least until such limitation is lifted. Kind regards, Mart=C3=ADn --=20 Mart=C3=ADn Marqu=C3=A9s It=E2=80=99s not that I have something to hide, it=E2=80=99s that I have nothing I want you to see