Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 4E2161AA4963 for ; Sat, 31 Mar 2012 09:26:19 -0300 (ADT) Received: from delta01.pnet.xcon.it ([62.48.53.16]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SDxNn-0006rQ-OY for pgsql-hackers@postgresql.org; Sat, 31 Mar 2012 12:26:19 +0000 Received: from localhost (localhost [127.0.0.1]) by delta01.pnet.xcon.it (Postfix) with ESMTP id A6C84103DDD69; Sat, 31 Mar 2012 14:26:02 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at delta01.pnet.xcon.it Received: from delta01.pnet.xcon.it ([127.0.0.1]) by localhost (delta01.pnet.xcon.it [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7wYCIs-W5dFY; Sat, 31 Mar 2012 14:26:01 +0200 (CEST) Received: from Gabriele.local (unknown [95.233.14.85]) (Authenticated sender: gabriele.bartolini@devise.it) by delta01.pnet.xcon.it (Postfix) with ESMTPSA id 471341029E219; Sat, 31 Mar 2012 14:26:01 +0200 (CEST) Message-ID: <4F76F7CF.2070908@2ndQuadrant.it> Date: Sat, 31 Mar 2012 14:25:51 +0200 From: Gabriele Bartolini User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Gilles Darold CC: pgsql-hackers@postgresql.org, Magnus Hagander , Fujii Masao , Bernd Helmle , Euler Taveira de Oliveira , Marti Raudsepp Subject: Re: Patch pg_is_in_backup() References: <4F26E291.9020605@dalibo.com> <4F2B470F.5070107@timbira.com> <691525170451D3F76CEF7ED1@apophis.local> <4F50E1B0.90808@dalibo.com> In-Reply-To: <4F50E1B0.90808@dalibo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201203/1898 X-Sequence-Number: 205779 Hi Gilles, first and foremost, sorry for jumping in this thread so late. I read all previous discussions and I'd be happy to help you with this patch. > Agreed and sorry for the response delay. I've attached 2 patches here, > the first one is the same as before with just the renaming of the > function into pg_is_in_exclusive_backup(). My quick response: I really like the idea of having a function that simply returns a boolean value. To be honest, I would have called it pg_is_in_backup() as you originally did - after all, I do not execute pg_start_exclusive_backup() or pg_stop_exclusive_backup(). It is more intuitive and pairs with pg_is_in_recovery(). I have never found any mention whatsoever in the documentation that talks about exclusive backup, and I am afraid it would generate confusion. However, I leave this up to the rest of the community's judgement (here is my opinion). I agree also that a function that returns the timestamp of the start of the backup might be useful. My opinion with the 'exclusive' keyword applies here too (I would simply name it pg_backup_start_time()). Finally, I tried to apply the patch but it looks like we need a new version that can apply with current HEAD. If you can do that, I am happy to assist with the review. Have a good weekend. Thank you, Gabriele -- Gabriele Bartolini - 2ndQuadrant Italia PostgreSQL Training, Services and Support gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it