| 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 22:56:02 |
| Message-ID: | 317001.1735858562@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:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2025-01-02 22:58:35 | Re: Fwd: Re: A new look at old NFS readdir() problems? |
| Previous Message | Larry Rosenman | 2025-01-02 22:50:22 | Re: Fwd: Re: A new look at old NFS readdir() problems? |