| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_checksums --help synopsis is quite long |
| Date: | 2019-08-23 17:21:44 |
| Message-ID: | alpine.DEB.2.21.1908231913200.8996@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bonjour Michaël,
> It would like to keep "data checksums" in the output,
You can do as you feel.
>>> I have decided that PostgreSQL is a mouthful, thus I'm rather using
>>> "Postgres".
>>
>> Changing that in one tool and not everything would of course be really
>> silly. And if you want to bring up the renaming again, please do so on
>> pgsql-advocacy as a separate topic :)
>
> Indeed. The official spelling is still "PostgreSQL".
Yep. I'm using "Postgres" wherever & whenever I can as a personal choice,
but I'm not planning to campaign about it. Now, it is good to know that
"postgres.org" seems owned by the project.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-08-23 17:26:38 | Re: WIP/PoC for parallel backup |
| Previous Message | Anastasia Lubennikova | 2019-08-23 17:14:26 | Re: Optimize single tuple fetch from nbtree index |