| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Christoph Berg <myon(at)debian(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Direct I/O |
| Date: | 2023-05-01 00:00:01 |
| Message-ID: | 2125851.1682899201@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Sun, Apr 30, 2023 at 06:35:30PM +1200, Thomas Munro wrote:
>> What about a
>> warning message about that at startup if it's on?
> Such a warning wouldn't be particularly likely to be seen by someone who
> already didn't read/understand the docs for the not-feature that they
> turned on.
Yeah, I doubt that that would be helpful at all.
> Since this is -currently- a developer-only feature, it seems reasonable
> to rename the GUC to debug_direct_io, and (at such time as it's
> considered to be helpful to users) later rename it to direct_io.
+1
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-05-01 02:47:57 | Re: Direct I/O |
| Previous Message | Michael Paquier | 2023-04-30 23:59:44 | Re: Autogenerate some wait events code and documentation |