| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
| Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>, Tristan Partin <tristan(at)neon(dot)tech>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
| Subject: | Re: Better help output for pgbench -I init_steps |
| Date: | 2023-07-13 11:29:45 |
| Message-ID: | 5ef6d298-31be-a754-e7f8-631e9a591f06@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12.07.23 19:47, Gurjeet Singh wrote:
>> If you end up with variant 3 or 4, please use double quotes instead of
>> single quotes.
>
> Will do.
>
> I believe you're suggesting this because in the neighboring help text
> the string literals use double quotes. I see that other utilities,
> such as psql also use double quotes in help text.
>
> If there's a convention, documented somewhere in our sources, I'd love
> to know and learn other conventions.
https://www.postgresql.org/docs/devel/error-style-guide.html#ERROR-STYLE-GUIDE-QUOTATION-MARKS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2023-07-13 12:02:36 | Potential memory leak in contrib/intarray's g_intbig_compress |
| Previous Message | Peter Eisentraut | 2023-07-13 11:27:33 | Re: Consistent coding for the naming of LR workers |