Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sWyIg-000mAh-Uz for pgsql-general@arkaria.postgresql.org; Thu, 25 Jul 2024 13:14:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sWyId-00EwVF-Si for pgsql-general@arkaria.postgresql.org; Thu, 25 Jul 2024 13:14:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sWyId-00EwV6-Hg for pgsql-general@lists.postgresql.org; Thu, 25 Jul 2024 13:14:27 +0000 Received: from mail-ot1-x329.google.com ([2607:f8b0:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sWyIa-001NMi-RD for pgsql-general@postgresql.org; Thu, 25 Jul 2024 13:14:26 +0000 Received: by mail-ot1-x329.google.com with SMTP id 46e09a7af769-70362cb061aso474710a34.1 for ; Thu, 25 Jul 2024 06:14:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721913264; x=1722518064; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=NdOzQMbQRYqI836JFV1dbdf26ynie1ZSGYGi5APClvk=; b=TP6vV88vQTIHqSBl+nDugcIHLBHZAyyl0V3oKpAz+fXry+p7s0yP184HnrRht6BCsy 52lgcKkSYOKG3s1ErGwv/nZmfoyWZfTtmyOMpRSyjcm8d2yazlJlzLq2GARNGU1so5/I ShiJrvs6DMkygsSJJrK3bmDaEuhh+8ihJV56nFtW0IAMGHDAc04G45yQwA+xuN0jprl4 tu/I6qO9KXkgtKuEeXThDdZpVYLZ07fDtwrd86oD++7ANkRSwa25ortPsPDZ6VNsMuQG B2kbAXkhYGZ730UOyl4OTo1zaZEAtoaODyZv/JI6WesM886wSf6Lpo/0bYnlmoMAxuNW sB7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721913264; x=1722518064; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NdOzQMbQRYqI836JFV1dbdf26ynie1ZSGYGi5APClvk=; b=sAvsAunEMspyELUQh8AdjHQ3qVEs6HQQOiZ1yhrrFUrd6OUx8H1pps8V9Hv7ma18Y+ x8jmnwO7n6xZ3w6s2Gm/DQZzA1B1LuJ3k2lOvbfurCKNYiB40ZBh+bwVXOOwaroiFpFM 9Qqnks+5Xd/dx7e+6D6tdkxqSkOktjuy7024tr8/70BhjMnZcWQhaLYfFYxaCSNfBQLY 6grku1wNnbya8BjuvQn7SP+5147dXL3j+8hSicxyrAycPjzikLn36uPFtsRAggu9sq1h 7TQ6gkrSxXYamR8CyjFT5HAHyQHOaC4XkCC4EOuL6VyxJDZoQyXSM81ZF1DnIwMv3jAN 8kJA== X-Gm-Message-State: AOJu0YzF4Xk3LLkUkv5OCSU/829fXTY01dLsOJ1jRsrn3wx4ijp4dtpC /KehTdltLOHTicszmlAZ8AkIg4K9qCGc0O2LgE/LCOS7YHtMzxs1VibkpmurRQkgkGbjx1tVmA6 s72thCAv/iKHiju5C/+Kyp3hG4izWlg== X-Google-Smtp-Source: AGHT+IHBrCehvwaRNv7wN8zg6n5auZMackJLjdvm6NsJMU15xgZgFqN6q7UG3HKtK3/5gCvRHH3OeyBRjQtZs+1hkzM= X-Received: by 2002:a05:6870:d612:b0:261:7af:719c with SMTP id 586e51a60fabf-266eddc17aamr2071943fac.35.1721913263773; Thu, 25 Jul 2024 06:14:23 -0700 (PDT) MIME-Version: 1.0 References: <3332.1717019021@sss.pgh.pa.us> In-Reply-To: From: Ron Johnson Date: Thu, 25 Jul 2024 09:14:12 -0400 Message-ID: Subject: Re: Memory issues with PostgreSQL 15 To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006bdfb3061e122c2e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006bdfb3061e122c2e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jul 25, 2024 at 6:59=E2=80=AFAM Christian Schr=C3=B6der < christian.schroeder@wsd.com> wrote: > Hi all, > I started this discussion in May and was then dragged into other topics, > so I could never follow up. Sorry for that! > Since then, the problem has resurfaced from time to time. Right now, we > seem to have issues again, which gives me the opportunity to follow up on > your various suggestions. > > The current error messages are similar to what we have seen before: > > <2024-07-25 12:27:38 CEST - > LOG: could not fork autovacuum worker > process: Cannot allocate memory > <2024-07-25 12:27:38 CEST - mailprocessor> ERROR: could not resize share= d > memory segment "/PostgreSQL.1226901392" to 189280 bytes: No space left on > device > What's mailprocessor? Maybe it's using some tmpfs device. > > --0000000000006bdfb3061e122c2e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jul 25, 2024 at 6:59=E2=80=AFAM C= hristian Schr=C3=B6der <c= hristian.schroeder@wsd.com> wrote:
Hi all,
I started this discussion in May and was then dragged into other topics, so= I could never follow up. Sorry for that!
Since then, the problem has resurfaced from time to time. Right now, we see= m to have issues again, which gives me the opportunity to follow up on your= various suggestions.

The current error messages are similar to what we have seen before:

<2024-07-25 12:27:38 CEST - > LOG:=C2=A0 could not fork autovacuum wo= rker process: Cannot allocate memory
<2024-07-25 12:27:38 CEST - mailprocessor> ERROR:=C2=A0 could not res= ize shared memory segment "/PostgreSQL.1226901392" to 189280 byte= s: No space left on device

What's m= ailprocessor?=C2=A0 Maybe it's using some tmpfs device.

--0000000000006bdfb3061e122c2e--