Re: Fwd: Re: A new look at old NFS readdir() problems?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: David Steele <david(at)pgbackrest(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-08 20:21:27
Message-ID: 1688119.1736367687@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Will people now always get a clear error on failure? Crazy idea, but
> could we have initdb or postmaster start test this?

It'd require adding quite a lot of cycles: I'd guess you'd need to
create/drop a hundred or a thousand files to be sure of seeing the
problem.

Another problem is that even if the primary data directory is okay,
a tablespace could be created on a filesystem that's not okay.

I doubt that it's worth it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2025-01-08 20:21:46 Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?
Previous Message Andres Freund 2025-01-08 20:07:24 Re: use a non-locking initial test in TAS_SPIN on AArch64