public inbox for [email protected]
help / color / mirror / Atom feedFrom: Koen De Groote <[email protected]>
To: PostgreSQL General <[email protected]>
Subject: Running docker in postgres, SHM size of the docker container in postgres 16
Date: Tue, 19 Nov 2024 23:22:18 +0100
Message-ID: <CAGbX52GNvsV-sNAS36LwmFOc2Qsn74ZA31T_GNJNeBYATJGBAw@mail.gmail.com> (raw)
Hello all,
Assume a machine with 16 CPU cores and 64GB of RAM. 300 max connections.
Postgres is running here, inside a docker container. Docker containers
receive a small amount of shared memory from /dev/shm
Experience teaches that the default 64MB of /dev/shm for the postgres
container, is not enough for databases of even 50GB in size. Previously
I've increased the /dev/shm setting to 256MB for the postgres container.
Issues that made this necessary all came in the form of too many queries
running at once, asking too much memory space, I assume.
I recently upgraded a setup from postgres 11 to postgres 16 via logical
replication, and found that running "vacuum(analyze, verbose)" fails unless
I give the container 1GB of /dev/shm. Where previously 256MB sufficed on
the old postgres 11 version.
Why would that be? It's the exact same data. The install is about 50GB in
size. Is there something wrong with postgres 16, or did some settings
significantly change, that I need to know about? I went over all the
changelogs, nothing stood out as relevant to this, but that might be a lack
of experience on my end.
Regards,
Koen De Groote
view thread (4+ 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]
Subject: Re: Running docker in postgres, SHM size of the docker container in postgres 16
In-Reply-To: <CAGbX52GNvsV-sNAS36LwmFOc2Qsn74ZA31T_GNJNeBYATJGBAw@mail.gmail.com>
* 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