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 1sCEbb-0047GA-8d for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 08:24:20 +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 1sCEba-00EBMK-Ha for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 08:24:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sCEba-00EBMB-1V for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 08:24:18 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCEbX-001JUV-4V for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 08:24:17 +0000 Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-52a54d664e3so690117e87.0 for ; Wed, 29 May 2024 01:24:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peoplecall-com.20230601.gappssmtp.com; s=20230601; t=1716971054; x=1717575854; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5MyMwAK8aK5tEupN06GLowLO1czpL98X641avKN0Mpo=; b=ZBte7UFyYfjwG/g00ZoTTqscjfjBcrZ4fO3T++UJ6lT1JaTMJ4eaRR66Co8Y8bil1g 8Dv00c2V8iaOnj0F4+mSlqbnLFkSuVBmgCe+pCHRw1riAQ4OYKHMo97FGaDH1Wbi/n5Q 5aWKPSp556NUfhL16Rh5uKkEvkUhlt6Fq40GG1ewRZV+WV1MMoPwNkuwmTfGdNSNNyzm AQq1UI4/bz7GfyC2JizD0teCshnaxAffET9IvK7N/MXqfqS4j0PV/vveQNDWrTkxxkIy gjTK5ZMdwLHN6CxfFLoyz+o8JtQ4040XG0x7kUAgHGzNC3HCZz2WDvywimDrgbD3F2wx 1G5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716971054; x=1717575854; h=content-transfer-encoding:cc: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=5MyMwAK8aK5tEupN06GLowLO1czpL98X641avKN0Mpo=; b=H3uYOSc9VkUCg7IroNWEgh/hmSJM0s/4rnR3Pg0g0QV0OxExkd4RLEwY8tWANeLP36 QYCCtPdZ5CUGndfW1UHyV5Ch9jXzWX7vw681qxuqpccDnb38gssPj8soapbXoI5lLo1Q lvXXHfgisg1oClZ30cUjQIQtbKWpy0FVW8RLusMADH8cYObIcTDdEeWn9ou0CZ+fxynM iMYdJ1CSfBT0Uj6KVrbzHSNTyBWiaEHxVD/1rVPZ5wYY/n1gZzEbf1y3B6veqcl06xGL 2/2aZtcZIoYONr8iicF32AO9y4HSK4YZOU+3h7fMi/VS7JOeefq71+mTKhU2Mh7JHg3m RolQ== X-Gm-Message-State: AOJu0YzZPekMz5HG3yKnKLsRT+3JgBA7u6VrUJpMiJHY/rpjStLMsilY xFrn0OQpd3jTqpROGdrsAKZ+BLlnt0Se2SSgEj4fVgOmi1m1GcSF7lKVK8KuVbuMhnjBfqGDv9D bRn9TDcT0lRhorFkwAEm8SJLPVLUg4IlKF9fDcqSQPNw1T5Y= X-Google-Smtp-Source: AGHT+IEZ8yv4NyvXEizRC8f+54d9uqB0mio1qiipD/4iB5JvDlFf93TXrMMfLO6naUSRyyI+p7c3iIFjRZ570YGRKGM= X-Received: by 2002:a05:6512:4cc:b0:51e:f2bb:158a with SMTP id 2adb3069b0e04-52966ca8c0fmr8890847e87.64.1716971054217; Wed, 29 May 2024 01:24:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Francisco Olarte Date: Wed, 29 May 2024 10:23:38 +0200 Message-ID: Subject: Re: Memory issues with PostgreSQL 15 To: =?UTF-8?Q?Christian_Schr=C3=B6der?= Cc: "pgsql-general@lists.postgresql.org" , Eric Wong 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 Christian: On Wed, 29 May 2024 at 00:59, Christian Schr=C3=B6der wrote: > Thank you for your advice. I used "ipcs" to get more readable information= about the shared memory: ... > As far as I understand, there is no upper limit to the size of the shared= memory. The database only holds a single shared memory segment, which does= n't seem to have a relevant size. Seems the same to me, so I will disregard that. > I am surprised to see this since I would have expected much more shared m= emory to be used by the database. Is there anything in the configuration th= at prevents the shared memory from being used? I am not too current with postgres, that one was a thing which happened to me when I did more administration, and is one you always want to check. I assume you have all checked, but I would follow by insuring every mounted partition in your system has space. I am not current on the details, but I know Pg can be mmaping things and doing other stuff. Your problem seems more of resource exhaustion, so I would follow by checking that, both disk, tmpfs and all the other stuff. I cannot give you advice on that as it depends a lot on your server configuration and from the age in the mssages I suspect you have the usual suspects debugged. But as you have a configuration crahsing in minutes and it seems to be a dev server you could do it easily. Sorry. Francisco Olarte.