From: | David Steele <david(at)pgbackrest(dot)org> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Larry Rosenman <ler(at)lerctr(dot)org>, Pgsql hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Fwd: Re: A new look at old NFS readdir() problems? |
Date: | 2025-01-06 16:41:20 |
Message-ID: | 606e3ceb-0535-40ca-9d31-ecb2c4a8b4b5@pgbackrest.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/4/25 11:07, Thomas Munro wrote:
> On Sat, Jan 4, 2025 at 5:48 AM David Steele <david(at)pgbackrest(dot)org> wrote:
>> We had one issue reported [1] involving Alpine Linux and CIFS and
>
> Not directly relevant for pgbackrest probably, but I noticed that
> Alpine comes up in a few reports of failing rm -r on CIFS. I think it
> might be because BSD and GNU rm use fts to buffer pathnames in user
> space (narrow window), while Alpine uses busybox rm which has a
> classic readdir()/unlink() loop:
Yeah, this doesn't affect pgBackRest because we have our own rmtree that
uses snapshots (for the last few years, at least).
> As for CIFS, there are lots of reports of this sort of thing from
> Linux CIFS clients.
There may be users running Postgres on CIFS but my guess is that is rare
-- at least I have never seen anyone doing it.
I'm more concerned about the report we saw on SUSE/NFS [1]. If that
report is accurate it indicates this may not be something we can just
document and move on from -- unless we are willing to entirely drop
support for NFS.
Regards,
-David
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2025-01-06 16:51:29 | Re: Adjusting hash join memory limit to handle batch explosion |
Previous Message | Andres Freund | 2025-01-06 16:28:39 | Re: AIO v2.0 |