Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 77F61197AB8A for ; Mon, 30 Jan 2012 17:16:40 -0400 (AST) Received: from oproxy7.bluehost.com ([2605:dc00:100:2::a7] helo=oproxy7-pub.bluehost.com) by magus.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Rryaa-0000Jl-2Y for pgsql-hackers@postgresql.org; Mon, 30 Jan 2012 21:16:40 +0000 Received: (qmail 22613 invoked by uid 0); 30 Jan 2012 21:16:19 -0000 Received: from unknown (HELO host159.hostmonster.com) (74.220.207.159) by oproxy7.bluehost.com with SMTP; 30 Jan 2012 21:16:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=timbira.com; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=ozT6n6vnRxpw+Q2OmtGJLRLduAEYw1EaBzDmRLabubU=; b=VqcdYR1AMsoowTIh4RMMLe/SHk0eoYbYwig/MOrHQrY/VT343FSP1bdy9yzw4wYs6DTxyUiWw0eiGFGpFa0jzLDFUL3OlrNuDfDUSUV5BzHK3etmXZpQH0gUaUOnFbGD; Received: from [177.0.92.243] (helo=[10.3.2.6]) by host159.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RryaI-0006YD-Dj; Mon, 30 Jan 2012 14:16:19 -0700 Message-ID: <4F27081D.2050000@timbira.com> Date: Mon, 30 Jan 2012 18:14:05 -0300 From: Euler Taveira de Oliveira User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 MIME-Version: 1.0 To: Gilles Darold CC: pgsql-hackers@postgresql.org Subject: Re: Patch pg_is_in_backup() References: <4F26E291.9020605@dalibo.com> In-Reply-To: <4F26E291.9020605@dalibo.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Identified-User: {1651:host159.hostmonster.com:timbirac:timbira.com} {sentby:smtp auth 177.0.92.243 authed with euler@timbira.com} X-Pg-Spam-Score: -2.0 (--) X-Archive-Number: 201201/1703 X-Sequence-Number: 202290 On 30-01-2012 15:33, Gilles Darold wrote: > Yesterday I was facing a little issue with a backup software (NetBackup) > that do not report error when a post backup script is run. The problem > is that this script execute pg_stop_backup() and if there's any failure > PostgreSQL keeps running in on-line backup mode. So the backup is not > completed and the next one too because the call to pg_start_backup() > will fail. > I use something similar to your pl/PgSQL version and was about to propose something along these lines to core. +1 to include it. Please, add your patch to the next CF. -- Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/ PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento