Ron writes:
> On 9/22/22 09:34, Tom Lane wrote:
>
>> Ron 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_dum
On 9/22/22 09:34, Tom Lane wrote:
Ron 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
eve
Ron 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
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.
But however much I search the log file for strings like ERROR, FATAL, WARN,
INFO, and "archiver", I don't see
