From: Олег Самойлов <splarv@ya.ru>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Return codes for archive and restore commands
Date: Mon, 3 Dec 2018 18:52:44 +0300
Message-ID: <567B704B-90EF-4442-AED0-54F976AFEEAA@ya.ru> (raw)
In-Reply-To: <20181129022347.GH626@paquier.xyz>
References: <154340283171.1324.10549444217937216132@wrigleys.postgresql.org>
<20181129022347.GH626@paquier.xyz>
> If you were to rewrite those paragraphs or make them more precise, how
> would you actually shape your suggestions? I personally quite like the
> current formulations, but I am rather used to it to be honest.
> --
> Michael
Yep, I am for make them more precise. Now this paragraphs describe PostgreSQL and bash behavior for users of PostgreSQL and may be they are good in this. But for a script or application programmer must be described not only behavior of PostgreSQL, but also precisely described the program interface. For instance, aws cli utility, that I used for my archive and restore commands sometimes return 255 code, for instance, in a case of network fault to connect to S3 (object get command). And I was surprised that the PostgreSQL suddenly stoped in such case, there was nothing in documentation about this. So explicitly describing behavior of PostgreSQL in terms of script returning codes will be useful for script programmes.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: splarv@ya.ru, michael@paquier.xyz, pgsql-docs@lists.postgresql.org
Subject: Re: Return codes for archive and restore commands
In-Reply-To: <567B704B-90EF-4442-AED0-54F976AFEEAA@ya.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox