From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Brown <michael(dot)brown(at)discourse(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: should frontend tools use syncfs() ? |
Date: | 2023-09-27 12:56:08 |
Message-ID: | 42804669-7063-1320-ed37-3226d5f1067d@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17.08.23 04:50, Michael Paquier wrote:
>> Yeah, this crossed my mind. Do you know of any existing examples of
>> options with links to a common section? One problem with this approach is
>> that there are small differences in the wording for some of the frontend
>> utilities, so it might be difficult to cleanly unite these sections.
> The closest thing I can think of is Color Support in section
> Appendixes, that describes something shared across a lot of binaries
> (that would be 6 tools with this patch).
I think it's a bit much to add a whole appendix for that little content.
We have a collection of platform-specific notes in chapter 19, including
file-system-related notes in section 19.2. Maybe it could be put there?
From | Date | Subject | |
---|---|---|---|
Next Message | Hayato Kuroda (Fujitsu) | 2023-09-27 12:58:54 | RE: [PGdocs] fix description for handling pf non-ASCII characters |
Previous Message | Masahiko Sawada | 2023-09-27 12:39:45 | Re: Testing autovacuum wraparound (including failsafe) |