Sorry for the the double post but it seems that my previous reply
doesn't reach the pgsql-hacker list. So here is the new patches that
limit lines to 80 characters.
Le 02/05/2012 19:53, Gabriele Bartolini a écrit :
> 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.
Administrateur de bases de données
http://dalibo.com - http://dalibo.org
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-05-15 02:43:35|
|Subject: Re: Bugs in our Windows socket code |
|Previous:||From: Simon Riggs||Date: 2012-05-14 23:31:20|
|Subject: Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable
value rather than the latest value|