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 ) id 1ptke9-00053w-AM for pgsql-admin@arkaria.postgresql.org; Tue, 02 May 2023 07:42:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ptke7-0001eW-Cn for pgsql-admin@arkaria.postgresql.org; Tue, 02 May 2023 07:41:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ptke7-0001eM-0H for pgsql-admin@lists.postgresql.org; Tue, 02 May 2023 07:41:59 +0000 Received: from mail-yw1-x112b.google.com ([2607:f8b0:4864:20::112b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ptkdz-0005aF-RZ for pgsql-admin@lists.postgresql.org; Tue, 02 May 2023 07:41:58 +0000 Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-55a010774a5so35786217b3.3 for ; Tue, 02 May 2023 00:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683013310; x=1685605310; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=9pTgzgcOkQOqAZXAG6e16trHVrfWZDpYMf7UfBBrAnk=; b=dru4Lp7mGxCIDZpzI6m3uXCPJmafJZZppNdGIfALrz/mTmmlxrdKKlAO1s7TOOq/jS EvR0brCW116/Kz/ASUyCF85NSNFakb0roxR/PvW768LJXWLRzlJnzi5GYjCbSzmcAi8f JD/Y5QLTmxi4K20COtn/XMDc9WRz6E32k/8oswi1+DjVpm+109z0HZQAkC5hr8A46RJK 40uiP153sddUjki2+lWUwFjQvQ4iTlq2Ls5R3oc1Fvy6e5mxfxj14Wlri0GawVqMBHom /ZThlYX+xHY1f+J4dScw738SloOU52reMw1dcCZNIrgm92PvYS+wspLKps0JWlwZSHZ9 /m8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683013310; x=1685605310; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9pTgzgcOkQOqAZXAG6e16trHVrfWZDpYMf7UfBBrAnk=; b=U/LjVyoT/VXQop11Yp/ib+EpTRp0G1d8+2sx2S21BLg/yNXx2fv+KNVD0QnLmMR36H +e8kDewPCf4vQubhQU7L3Y0NoqFa+NGpE4G0JM1RG38LhYlmDACmWmKP70j4UL0ggubt GeUdAv1pdPFA74N7+VBc0pxMUZn0oCl6ZM07KKIbH2T1qN2IOerthobP7Zq3tsfkPvE3 tOIWmoBEf/nMaKxXmZJ79ir6D/Vd0x1p901qbI3GnKu6eoYo4ltYPYzBct5YDNNugm2N z0qsf0GXY8uGsLeKXFGhD7b0ernDkvuFLliMJowv9ycXr8zQo+MRL2oxicrQejNAHBXd cvUw== X-Gm-Message-State: AC+VfDxjJOQwrjRjSkXaDktxWAnOeElZ4w5sME37C4zBbArHgbEpht+D 04Ms7RocDt/soMZmackG4o3oTFmaHo4= X-Google-Smtp-Source: ACHHUZ7iFWZ3S2h92bo3eFZ3N4JVH0LjXLW9N/XDWNplQTHIDJ6wyhmypkQkpYt8SqlvdT8H3bZrUg== X-Received: by 2002:a0d:ead4:0:b0:55a:97f3:7a2d with SMTP id t203-20020a0dead4000000b0055a97f37a2dmr1347362ywe.38.1683013309988; Tue, 02 May 2023 00:41:49 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:d08:786:d5c1:fde6? ([2600:1700:bd2c:b810:d08:786:d5c1:fde6]) by smtp.googlemail.com with ESMTPSA id u5-20020a0dd205000000b0054f9e7fed7asm7889177ywd.137.2023.05.02.00.41.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 May 2023 00:41:49 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------0QZfL0UHzZbc0bJk3HmT7WlM" Message-ID: Date: Tue, 2 May 2023 02:41:47 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: pg_dump why no indicator of completion Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <6EF026A5-5CEC-48AB-B27E-C225DAE6E10A@elevated-dev.com> <491f094b-93f9-6a7d-1846-901aa583171c@gmail.com> <525021224.1417508.1682996739307@office.mailbox.org> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------0QZfL0UHzZbc0bJk3HmT7WlM Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/1/23 22:21, Tim wrote: >  > After reading the responses in this thread I've adjusted it to capture > the exit status > > Just so I'm not a complete troll, heres your example which also appends a > success/fail message :) > > nohup $(pg_dump ${connection_details} > something.log 2>&1 && echo "pgdump > succeded" >> something.log || echo "pgdump failed" something.log) & Out of curiosity, why this:     > something.log 2>&1 instead of that?     &> something.log Yes, "&>" is a bashism, but so what? -- Born in Arizona, moved to Babylonia. --------------0QZfL0UHzZbc0bJk3HmT7WlM Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 5/1/23 22:21, Tim wrote:
 > After reading the responses in this thread I've adjusted it to capture the exit status

Just so I'm not a complete troll, heres your example which also appends a success/fail message :)

nohup $(pg_dump ${connection_details} > something.log 2>&1 && echo "pgdump succeded" >> something.log || echo "pgdump failed" something.log) &

Out of curiosity, why this:
    > something.log 2>&1
instead of that?
    &> something.log

Yes, "&>" is a bashism, but so what?

--
Born in Arizona, moved to Babylonia.
--------------0QZfL0UHzZbc0bJk3HmT7WlM--