Re: Direct I/O

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-08 21:31:02
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2023-04-08 17:10:19 -0400, Tom Lane wrote:
>> (BTW, why are the log lines doubly timestamped?)

> It's odd.

Oh, I guess that's intentional, because crake has

'log_line_prefix = \'%m [%s %p:%l] %q%a \'',

> It's also odd that it's just crake having the issue. It's just a linux host,
> afaics.

Indeed. I'm guessing from the compiler version that it's Fedora 37 now
(the lack of such basic information in the meson configuration output
is pretty annoying). I've been trying to repro it here on an F37 box,
with no success, suggesting that it's very timing sensitive. Or maybe
it's inside a VM and that matters?

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-04-08 21:42:14 Re: Direct I/O
Previous Message Andres Freund 2023-04-08 21:23:37 Re: Direct I/O