Re: Direct I/O

From: Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: 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 <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Direct I/O
Date: 2023-04-16 07:54:15
Message-ID: 56954054-fc8c-22a2-4ff7-ad0fe7357f16@mksoft.nu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-04-16 00:10, Tom Lane wrote:

> so curculio should be the only one that's at risk here.
> Maybe just upgrading it is the right answer.

Just let me know if I should switch curculio to OpenBSD 7.3.

I already have a new server setup so only need to switch the "animal"
and "secret" and enable the cron job to get it running.

/Mikael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-16 10:14:35 Can we delete the vacuumdb.sgml notes about which version each option was added in?
Previous Message David Rowley 2023-04-16 05:29:34 Re: Protecting allocator headers with Valgrind