public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Christian Schröder <[email protected]>
Cc: Francisco Olarte <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Eric Wong <[email protected]>
Subject: Re: Memory issues with PostgreSQL 15
Date: Wed, 29 May 2024 14:43:41 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <LO0P265MB2700F3C159F47D8F039D6B1FF9F12@LO0P265MB2700.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB2700E0D30CC9A427956FC121F9F02@LO0P265MB2700.GBRP265.PROD.OUTLOOK.COM>
	<CA+bJJbyzFdr1i1Yarqt=JnsN0WUg+veRvYZC1+kaYnWFGjiYRw@mail.gmail.com>
	<LO0P265MB2700F3C159F47D8F039D6B1FF9F12@LO0P265MB2700.GBRP265.PROD.OUTLOOK.COM>

=?utf-8?B?Q2hyaXN0aWFuIFNjaHLDtmRlcg==?= <[email protected]> writes:
> # ipcs -m

> ------ Shared Memory Segments --------
> key        shmid      owner      perms      bytes      nattch     status
> 0x04000194 35         postgres   600        56         19

> I am surprised to see this since I would have expected much more shared memory to be used by the database. Is there anything in the configuration that prevents the shared memory from being used?

SysV shared memory isn't that relevant to Postgres anymore.  Most
of what we allocate goes into POSIX-style shared memory segments,
which are not shown by "ipcs".  We do still create one small
fixed-size data structure in SysV memory, which is what you're
seeing here, for arcane reasons having to do with the lifespan of
the shared memory segments being different in those two APIs.

>> <2024-05-21 11:34:46 CEST - mailprocessor> ERROR:  could not resize
>> shared memory segment "/PostgreSQL.2448337832" to 182656 bytes: No
>> space left on device

This seems to indicate that you're hitting some kernel limit on
the amount of POSIX shared memory.  Not sure where to look for
that.

			regards, tom lane

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Memory issues with PostgreSQL 15
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox