Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elbe 2.2 requests more memory for PostgreSQL clusters than 1.2 did #148

Closed
manut opened this issue Apr 5, 2018 · 1 comment
Closed

Elbe 2.2 requests more memory for PostgreSQL clusters than 1.2 did #148

manut opened this issue Apr 5, 2018 · 1 comment
Labels

Comments

@manut
Copy link
Contributor

manut commented Apr 5, 2018

Building a wheezy image with elbe 2.2 results in a different PostgreSQL cluster configuration than with elbe 1.2. In particular the
+shared_buffers setting in /etc/postgresql/9.1/main/postgresql.conf differs - with elbe 1.2 it used to be:

shared_buffers = 24MB

while with elbe 2.2 it is:

shared_buffers = 32MB

The increased amount of shared buffer memory requested by PostgreSQL cannot be allocated on my hardware (existing product, which we still need to support) and
+the RDBMS fails to start.

Long story short: same XML, same build machine, same target device, different elbe version -> product broken.

This has probably something to do with the fact, that elbe 2.2 creates a Debian 8 (jessie) initvm while the 1.2 does Debian 7 (wheezy). Note, that the
+PostgreSQL conffiles in /etc/postgresql/ get generated upon package installation, so obviously some maintainer script works differently when run in chroot on
+Debian 8 and 7 - maybe the postinst script gets something from the host's environment that chroot cannot hide?

Any idea how to fix that?

Thanks & regards,
Lukasz

@bgermann bgermann changed the title Elbe 2.2 requests more memory for PostgreSQL clusters than 1.2 did, which Elbe 2.2 requests more memory for PostgreSQL clusters than 1.2 did Sep 2, 2019
@bgermann
Copy link
Contributor

We will not change specific Debian package configurations via Elbe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants