Re: pg_dump failed with error code 255, but I don't see why

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump failed with error code 255, but I don't see why
Date: 2022-09-22 14:56:45
Message-ID: 992001c5-0241-c4b8-7788-7ea1954db7ae@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/22/22 09:34, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>> v9.6.2.23
>> I always run pg_dump with the --verbose option, and the bash script echos
>> $?, so there's a 25,664 line log file for me to examine which explicitly
>> shows the return code.
> A quick search of the 9.6 pg_dump source code shows that it only
> ever calls exit() with values 0 or 1. 255 would have to be coming
> from some outside factor. You sure your shell script isn't
> misbehaving and corrupting the reported return code?

Good to know.  The RC might be from ssh (the actual command being "ssh
postgres(at)HOSTNAME pg_dump ...".

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-09-22 15:16:43 Validate the internal consistency of pg_dump output?
Previous Message Tom Lane 2022-09-22 14:34:00 Re: pg_dump failed with error code 255, but I don't see why