From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Patrick Frießnegg <patrick(dot)fri(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: PG_DUMPALL not executable within docker container |
Date: | 2023-09-27 09:06:17 |
Message-ID: | 8B5FCBE7-AF0F-41C7-A425-C35A874D723F@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On 27 Sep 2023, at 10:43, Patrick Frießnegg <patrick(dot)fri(at)gmail(dot)com> wrote:
> root(at)13fba0e113c7:/# pg_dumpall
> popen failure: Cannot allocate memory
> pg_dumpall: error: program "pg_dump" is needed by pg_dumpall but was not found in the same directory as "/usr/lib/postgresql/15/bin/pg_dumpall"
pg_dumpall runs the pg_dump binary, so when starting up it locates and tries to
execute pg_dump to check its version. The above error indicates that the
binary does indeed exist, but when trying to execute it there is a problem with
the popen() call. A quick search reveals that this has been reported against
Docker (and has been fixed it seems):
https://github.com/docker-library/postgres/issues/1103
As this is not a bug in postgres, pgsql-general is probably a better
mailinglist to use for help.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Jet Zhang | 2023-09-27 09:06:45 | Bug of psql meta-command \sf & \sv |
Previous Message | Patrick Frießnegg | 2023-09-27 08:43:22 | PG_DUMPALL not executable within docker container |