Skip site navigation (1) Skip section navigation (2)

Re: Patch pg_is_in_backup()

From: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
To: Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>
Subject: Re: Patch pg_is_in_backup()
Date: 2012-05-02 17:53:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hi Gilles,

    Sorry for the delay.

Il 03/04/12 14:21, Gilles Darold ha scritto:
> +1, this is also my point of view.

    I have looked at the patch that contains both pg_is_in_backup() and 

    From a functional point of view it looks fine to me. I was thinking 
of adding the BackupInProgress() at the beginning of 
pg_backup_start_time(), but the AllocateFile() function already make 
sure the file exists.

    I have performed some basic testing of both functions and tried to 
inject invalid characters in the start time field of the backup_label 
file and it is handled (with an exception) by the server. Cool.

    I spotted though some formatting issues, in particular indentation 
and multi-line comments. Some rows are longer than 80 chars.

    Please resubmit with these cosmetic changes and it is fine with me. 
Thank you.


  Gabriele Bartolini - 2ndQuadrant Italia
  PostgreSQL Training, Services and Support
  gabriele(dot)bartolini(at)2ndQuadrant(dot)it |

In response to


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2012-05-02 18:04:59
Subject: Re: plpython crash (PG 92)
Previous:From: Magnus HaganderDate: 2012-05-02 17:42:47
Subject: Re: Have we out-grown Flex?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group