On Mon, Dec 08, 2025 at 11:23:53PM +0530, tushar wrote:
> I found a scenario where, after firing the wrong way of using the pg_dump
> command, not only server fail to start,
> But later, I am not able to perform initdb/pg_ctl as well
>
> Please refer to this testcase:
> "
> PG v19 devel, Cluster running on default port=5432
> Run pg_dump (./pg_dump -Ft -s -c -v -f postgres schema_clean.tar1)
> "
IIUC the problem is that you are overwriting the postgres binary. Is that
correct?
> Is there any way we can generate some error messages?
Perhaps it'd be worth making pg_dump a little more cautious about
overwriting existing files (or at least have the option to avoid that).
--
nathan