| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Noah Misch <noah(at)leadboat(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Direct I/O |
| Date: | 2023-04-09 16:35:29 |
| Message-ID: | 6afb4ce8-0b13-0278-7018-4c9f092148a7@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-04-09 Su 09:14, Andrew Dunstan wrote:
>
>
> On 2023-04-09 Su 08:39, Thomas Munro wrote:
>> On Sun, Apr 9, 2023 at 11:25 PM Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>> Didn't seem to make any difference.
>> Thanks for testing. I think it's COW (and I think that implies also
>> checksums?) that needs to be turned off, at least based on experiments
>> here.
>
>
>
> Googling agrees with you about checksums. But I'm still wondering if
> we shouldn't disable COW for the build directory etc. It is suggested
> at [1]:
>
>
> Recommend to set nodatacow – turn cow off – for the files that
> require fast IO and tend to get very big and get alot of random
> writes: such VMDK (vm disks) files and the like.
>
>
> I'll give it a whirl.
>
>
with COW disabled, I can no longer generate a failure with the test.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2023-04-09 18:50:50 | Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences |
| Previous Message | Tom Lane | 2023-04-09 16:23:50 | Re: cataloguing NOT NULL constraints |