Re: Dry-run mode for pg_archivecleanup - Mailing list pgsql-hackers

From Gabriele Bartolini
Subject Re: Dry-run mode for pg_archivecleanup
Date
Msg-id 4F1330F0.2010704@2ndQuadrant.it
Whole thread Raw
In response to Re: Dry-run mode for pg_archivecleanup  (Josh Kupershmidt <schmiddy@gmail.com>)
Responses Re: Dry-run mode for pg_archivecleanup
List pgsql-hackers
Hi Josh,

Il 15/01/12 01:13, Josh Kupershmidt ha scritto:
> I have signed on to review this patch for the 2012-01 CF. The patch
> applies cleanly, includes the necessary documentation, and implements
> a useful feature.
Thank you for dedicating your time to this matter.
> I think the actual debugging line:
>
> +                                       fprintf(stdout, "%s\n", WALFilePath);
My actual intention was to have the filename as output of the command, 
in order to easily "pipe" it to another script. Hence my first choice 
was to use the stdout channel, considering also that pg_archivecleanup 
in dry-run mode is harmless and does not touch the content of the directory.
> Oh, and I think the "removing file... " debug message above should not
> be printed in dryrun-mode, lest we confuse the admin.
Yes, I agree with you here.

Let me know what you think about my reasons for the stdout channel, then 
I will send v2.

Thanks again!

Ciao,
Gabriele

--  Gabriele Bartolini - 2ndQuadrant Italia PostgreSQL Training, Services and Support gabriele.bartolini@2ndQuadrant.it
|www.2ndQuadrant.it
 



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved
Next
From: "Kevin Grittner"
Date:
Subject: Re: pg_trigger_depth() v3 (was: TG_DEPTH)