| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | Thomas Munro <tmunro(at)freebsd(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, 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-02 23:05:13 |
| Message-ID: | 318051.1735859113@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Larry Rosenman <ler(at)lerctr(dot)org> writes:
> On 01/02/2025 4:56 pm, Tom Lane wrote:
>> I am sort of wondering though why we've not heard reports of this
>> many times before. Did FreeBSD recently change something in this
>> area? Also, if as they argue it's a fundamental problem in the NFS
>> protocol, why are we failing to reproduce it with other clients?
> Pre version 16, we worked just fine. There was a change in 16.
Well, as Thomas already mentioned, rmtree() used to work by reading
the directory and making an in-memory copy of the whole file list
before it started to delete anything. But reverting that wouldn't
fix all of the other problems that we now know exist. (In other
words, "we worked just fine" only for small values of "fine".)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-01-02 23:08:50 | Re: Fwd: Re: A new look at old NFS readdir() problems? |
| Previous Message | Larry Rosenman | 2025-01-02 22:58:35 | Re: Fwd: Re: A new look at old NFS readdir() problems? |