Re: Dry-run mode for pg_archivecleanup

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Gabriele Bartolini <gabriele(dot)bartolini(at)2ndquadrant(dot)it>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Dry-run mode for pg_archivecleanup
Date: 2012-01-27 22:55:55
Message-ID: 1327704842-sup-5100@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Josh Kupershmidt's message of vie ene 27 19:43:51 -0300 2012:
> On Fri, Jan 27, 2012 at 9:47 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> > This email thread seems to have trailed off without reaching a
> > conclusion.  The patch is marked as Waiting on Author in the
> > CommitFest application, but I'm not sure that's accurate.  Can we try
> > to nail this down?
>
> Perhaps my last email was a bit wordy. The only real change I am
> suggesting for Gabriele's patch is that the message printed to stderr
> when debug + dryrun are activated be changed to "would remove file
> ..." from "removing file", i.e around line 124:
>
> if (debug)
> fprintf(stderr, "%s: %s file \"%s\"\n",
> progname, (dryrun ? "would remove" : "removing"),
> WALFilePath);
>
> Other than that little quibble, I thought the patch was fine.

If you do that, please make sure you use two complete separate strings
instead of building one from spare parts. This bit is missing the _()
stuff though.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Klaver 2012-01-27 23:00:24 Re: pg_dump -s dumps data?!
Previous Message Josh Kupershmidt 2012-01-27 22:43:51 Re: Dry-run mode for pg_archivecleanup