From: Tom Lane <tgl@sss.pgh.pa.us>
To: markus.weyermann@gmx.net
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17315: Postgresql needs reinstall after restore
In-reply-to: <17315-cefb698e069aa044@postgresql.org>
References: <17315-cefb698e069aa044@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 04 Dec 2021 22:19:52 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2814158.1638720629.1@sss.pgh.pa.us>
Date: Sun, 05 Dec 2021 11:10:29 -0500
Message-ID: <2814159.1638720629@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2814159.1638720629%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> After restore, when trying to start postgres by "systemctl start postgres"
> errors are logged:

> /usr/lib/postgresql/14/bin/postgres: error while loading shared libraries:
> libicui18n.so.63: cannot open shared object file: No such file or
> directory

I don't see any reason to call that a Postgres bug.  Postgres certainly
did not remove that library --- even if it tried, it wouldn't have the
privileges to do so.  My guess is that you (or some administrative
process) incorrectly uninstalled that version of libicui18n some time ago,
but the existing PG server kept running because it had an open handle to
the shared library file.  After process shutdown, the kernel finished
removing the now-unreferenced library file, and then of course starting
PG up again would fail.

			regards, tom lane