| From: | Larry Rosenman <ler(at)lerctr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 22:58:35 |
| Message-ID: | 5510bb3943f6b0b1d6844e6e01ea898b@lerctr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/02/2025 4:56 pm, Tom Lane wrote:
> Larry Rosenman <ler(at)lerctr(dot)org> writes:
>> Would it make sense for ONLY drop database to have the above loop?
>
> Not really. We'd just be papering over the most-easily-observable
> consequence of readdir's malfeasance. There'd still be problems
> like basebackups omitting files, missed fsyncs potentially leading
> to data loss, etc.
>
> 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?
>
> regards, tom lane
Pre version 16, we worked just fine. There was a change in 16.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler(at)lerctr(dot)org
US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-01-02 23:05:13 | Re: Fwd: Re: A new look at old NFS readdir() problems? |
| Previous Message | Tom Lane | 2025-01-02 22:56:02 | Re: Fwd: Re: A new look at old NFS readdir() problems? |