| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Holger Jakobs <holger(at)jakobs(dot)com> |
| Cc: | PostgreSQL mailing list <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found |
| Date: | 2026-08-13 12:37:20 |
| Message-ID: | 20260813123719.GB329@p46.dedyn.io;lightning.p46.dedyn.io |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
Hi,
On Wed, Aug 12, 2026 at 12:50:57PM +0200, Holger Jakobs wrote:
> Today a pg_upgrade failed with this awkward message:
>
> Finding the real data directory for the source cluster ok
> Finding the real data directory for the target cluster sh: 1:
> (null)/postgres: not found
What was the exact command line you used?
> Obviously, cmd should contain the path of the oldbin directory, which is to
> be derived from the path of the pg_upgrade being called.
Are you saying you ran the 17 pg_update binary? I am not sure that is
supported/supposed to work, one should use the pg_upgrade binary from
the newer Postgres version (unless I misunderstood you).
Still, the error isn't great and should be improved / this case should
be caught earlier in pre-flight checks probably.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Tiwari | 2026-08-13 17:36:19 | Re: BUG #19617: Hash node can report incorrect actual rows number |
| Previous Message | Andrey Rachitskiy | 2026-08-13 12:01:02 | to_char() on integer with V format silently wraps on overflow |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Licio Matos | 2026-08-13 12:19:27 | Re: Urgent !!!! Tables inaccessible postgres v17.6 |