From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | noloader(at)gmail(dot)com |
Cc: | Evgeny Morozov <postgresql3(at)realityexists(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
Date: | 2023-05-06 22:29:24 |
Message-ID: | CA+hUKG+4n=Nz_brpBdLggfroGmvum_SYChS0PMu6GZLjBvTE8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, May 7, 2023 at 10:23 AM Jeffrey Walton <noloader(at)gmail(dot)com> wrote:
> This may be related... I seem to recall the GNUlib folks talking about
> a cp bug on sparse files. It looks like it may be fixed in coreutils
> release 9.2 (2023-03-20):
> https://github.com/coreutils/coreutils/blob/master/NEWS#L233
>
> If I recall correctly, it had something to do with the way
> copy_file_range worked. (Or maybe, it did not work as expected).
>
> According to the GNUlib docs
> (https://www.gnu.org/software/gnulib/manual/html_node/copy_005ffile_005frange.html)
>
> This function has many problems on Linux
> kernel versions before 5.3
That's quite interesting, thanks (we've been talking about making
direct use of copy_file_range() in a few threads, I'll definitely be
looking into that history), but we don't currently use
copy_file_range() or any coreutils stuff in the relevant code paths
here -- this data is copied by plain old pread() and pwrite().
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-05-07 01:21:30 | Re: "PANIC: could not open critical system index 2662" - twice |
Previous Message | Jeffrey Walton | 2023-05-06 22:22:06 | Re: "PANIC: could not open critical system index 2662" - twice |