| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ensure, not insure |
| Date: | 2023-11-08 07:31:28 |
| Message-ID: | CAApHDvr0MCvnTCwqh6PNbc2LOppj8s5YnHzMLC97Y8ojKo73sw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 8 Nov 2023 at 19:56, Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
> gettext_noop("The server will use the fsync() system call in several
> places to make "
> "sure that updates are physically written to disk. This insures "
> "that a database cluster will recover to a consistent state after "
> "an operating system or hardware crash.")
>
> ~
>
> I believe the word should have been "ensures"; not "insures".
I agree. It's surprisingly ancient, having arrived in b700a672f (June 2003).
> In passing I found/fixed a bunch of similar misuses in comments.
Those all look fine to me too.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2023-11-08 07:33:23 | Doubled test for SET statements in pg_stat_statements tests |
| Previous Message | Peter Eisentraut | 2023-11-08 07:31:00 | Re: Remove unnecessary 'always:' from CompilerWarnings task |