tushar <tushar.ahuja@enterprisedb.com> writes: > 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
> The result is : > edb@1a1c15437e7c bin]$ ./pg_dump -Ft -s -c -v -f postgres schema_clean.tar1 > qemu: uncaught target signal 7 (Bus error) - core dumped
I think what you are showing here is that you ran this command in the installation's bin directory, and where you write "-f postgres", that caused pg_dump to overwrite the postgres executable.
> Is there any way we can generate some error messages?
Don't do that. Generally speaking, you don't want installed files to be writable at all by ordinary user accounts ... but if they are, for heaven's sake don't cd into those directories before doing work. You're just setting yourself up for trouble.
right, that was unintentional 😊, Instead of "postgres", if i give any other name , i am getting an error e,g
[edb@1a1c15437e7c bin]$ ./pg_dump -Ft -s -c -v -f abc123 schema_clean.tar1 pg_dump: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: database "schema_clean.tar1" does not exist
So this query is a failed query and now if i give 'postgres' instead of 'abc123', Am I not supposed to get the same error , instead of
