From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Clean up some elog messages and comments for do_pg_stop_backup and do_pg_start_backup |
Date: | 2018-12-21 23:42:57 |
Message-ID: | 20181221234257.GF1948@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 21, 2018 at 10:43:57AM -0300, Alvaro Herrera wrote:
> errhint("Check that your archive_command is executing properly. "
> + "Backup can be canceled safely, "
> "but the database backup will not be usable without all the WAL segments.")))
>
> I think repeating the same term in the third line is not great. Some
> ideas:
>
> Backups can be canceled safely, but they will not be usable without all the WAL segments.
> The backup can be canceled safely, but it will not be usable without all the WAL segments.
> Database backups can be canceled safely, but the current backup will not be usable without all the WAL segments.
> Database backups can be canceled safely, but no backup will be usable without all the WAL segments.
Yes, I agree that repeating two times the work backup is not great.
What about the following then? This is your second proposal except
that the sentence refers to the backup current running using "this",
which shows better the context in my opinion:
"This backup can be canceled safely, but it will not be usable without
all the WAL segments.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-12-21 23:48:56 | Re: [PATCH] Improve tab completion for CREATE TABLE |
Previous Message | John Naylor | 2018-12-21 23:38:48 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |