Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1ptUam-0003Bf-Qz
	for pgsql-admin@arkaria.postgresql.org; Mon, 01 May 2023 14:33:28 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1ptUal-000700-Ng
	for pgsql-admin@arkaria.postgresql.org; Mon, 01 May 2023 14:33:27 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <rui@crazybean.net>)
	id 1ptUYs-0006zX-1A
	for pgsql-admin@lists.postgresql.org; Mon, 01 May 2023 14:31:30 +0000
Received: from impout007aa.msg.chrl.nc.charter.net ([47.43.20.31]
 helo=impout007.msg.chrl.nc.charter.net)
	by makus.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <rui@crazybean.net>)
	id 1ptUYl-002t26-7H
	for pgsql-admin@lists.postgresql.org; Mon, 01 May 2023 14:31:28 +0000
Received: from cerberus.crazybean.net ([71.11.29.254])
	by cmsmtp with ESMTP
	id tUYip5xCUMkkhtUYjpKgGq; Mon, 01 May 2023 14:31:22 +0000
Authentication-Results: crazybean.net; none
X-Authority-Analysis: v=2.4 cv=P/gpOwMu c=1 sm=1 tr=0 ts=644fcd3a
 a=GkUsAQdcAzAk0MT19QAIRQ==:117 a=GkUsAQdcAzAk0MT19QAIRQ==:17
 a=xqWC_Br6kY4A:10 a=P0xRbXHiH_UA:10 a=pGLkceISAAAA:8 a=TlktXNHwXu1LWHtd_uAA:9
 a=CjuIK1q_8ugA:10 a=yj-kMiFTTmPvN0TCZ8UA:9 a=g3f2hBo8vy9g0xlb:21
 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10
Received: from smtpclient.apple (<unknown>
 [2001:470:e117:4:7908:8dc3:df85:e93c])
	by cerberus.crazybean.net (OpenSMTPD) with ESMTPSA id 7903682a
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO);
	Mon, 1 May 2023 10:31:20 -0400 (EDT)
From: Rui DeSousa <rui@crazybean.net>
Message-Id: <8D0A91FC-C10C-4B68-9348-DA3F751FE470@crazybean.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2AA35439-B294-468F-A4E5-2A6E16D9D458"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Subject: Re: pg_dump why no indicator of completion
Date: Mon, 1 May 2023 10:31:18 -0400
In-Reply-To: 
 <CAGA3vBsyWKwJNPiYCu3juFfTqprb6FUK5gSH8zt29rqUzhtcLw@mail.gmail.com>
Cc: Frank Lanitz <frank@frank.uvena.de>,
 pgsql-admin@lists.postgresql.org
To: richard coleman <rcoleman.ascentgl@gmail.com>
References: 
 <CAGA3vBugp4Ce8ZbOfntb8HjCvo5QtX1hhAHj3iuCMZdzSTo4dg@mail.gmail.com>
 <61e421bc-d47f-05ef-edb2-bd9cbce1be40@frank.uvena.de>
 <CAGA3vBsyWKwJNPiYCu3juFfTqprb6FUK5gSH8zt29rqUzhtcLw@mail.gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.3)
X-CMAE-Envelope: 
 MS4xfGTG+yVnIl/Ik94kCzlZEduUvfNVJR+g6vp17oiwWipziByXWDHfL1yfidjU8XveOWNhO2jIc8Nsxb6NUN07R18YKG/rNic+fjc9MHHjrRC58K6tMK8Q
 rj1npkDc2y7vxo8LJH8o56+89aF9qAiPO+90OTGEZL9P3UUmjdJcAH/OejNtyw0h/LER8v3oK8c2yMADBBwnaGI0pep5rsvag2HA5zAJ/+WBAR7ASITaAcTJ
 oFnzv3rCUeeXoTckTNUA7CS4qKylOP8V9NoSU7GN78xY8Xx5Vm5g1S2Lf903e962
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/8D0A91FC-C10C-4B68-9348-DA3F751FE470%40crazybean.net>
Precedence: bulk


--Apple-Mail=_2AA35439-B294-468F-A4E5-2A6E16D9D458
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On May 1, 2023, at 10:00 AM, richard coleman =
<rcoleman.ascentgl@gmail.com> wrote:
>=20
> As I've mentioned in another response I typically run pg_dump as =
follows:
>=20
> nohup pg_dump {various settings} > something.log 2>&1 &

Why redirect standard error to standard out when using pg_dump? I assume =
that using standard out is not the backup stream.=20

If you want a success message in the log; write the success message to =
the log file if pg_dump exits successfully.=20

i.e.:   nohup pg_dump --verbose prod > prod.sql 2> prod.log && echo =
"Backup Completed Successfully!" >> prod.log &



--Apple-Mail=_2AA35439-B294-468F-A4E5-2A6E16D9D458
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On May 1, 2023, at 10:00 AM, richard coleman &lt;<a =
href=3D"mailto:rcoleman.ascentgl@gmail.com" =
class=3D"">rcoleman.ascentgl@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: 400; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">As =
I've mentioned in another response I typically run pg_dump as =
follows:<br class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><blockquote =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: 400; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; margin: 0px 0px =
0px 40px; border: none; padding: 0px;" class=3D""><div class=3D"">nohup =
pg_dump {various settings} &gt; something.log 2&gt;&amp;1 =
&amp;</div></blockquote></div></blockquote></div><br class=3D""><div =
class=3D"">Why redirect standard error to standard out when using =
pg_dump? I assume that using standard out is not the backup =
stream.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">If=
 you want a success message in the log; write the success message to the =
log file if pg_dump exits successfully.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">i.e.: &nbsp; <font face=3D"Courier New" =
class=3D"">nohup pg_dump --verbose prod &gt; prod.sql 2&gt; prod.log =
&amp;&amp; echo "Backup Completed Successfully!" =
&gt;&gt;&nbsp;prod.log&nbsp;&amp;</font></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_2AA35439-B294-468F-A4E5-2A6E16D9D458--