Re: Direct I/O

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Andrea Gelmini <andrea(dot)gelmini(at)gmail(dot)com>, 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-11 02:58:00
Message-ID: CA+hUKG+V=8dWyp6SOrA=Wh7WWemBR-bM_HYAp7EJOyyN+i9YdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 11, 2023 at 2:31 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> I tried to find out what POSIX says about this

(But of course whatever it might say is of especially limited value
when O_DIRECT is in the picture, being completely unstandardised.
Really I guess all they meant was "if you *copy* something that's
moving, who knows which bits you'll copy"... not "your data might be
incinerated with lasers".)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2023-04-11 03:03:27 Can we rely on the ordering of paths in pathlist?
Previous Message Thomas Munro 2023-04-11 02:53:51 Re: longfin missing gssapi_ext.h