| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Steele <david(at)pgbackrest(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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:41:45 |
| Message-ID: | 1690546.1736368905@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Steele <david(at)pgbackrest(dot)org> writes:
> On 1/8/25 12:40, Bruce Momjian wrote:
>> Will people now always get a clear error on failure?
> The error will be something like "directory is not empty" when trying to
> drop a database. So not very clear at all.
Conceivably we could adjust rmtree() to print a HINT mentioning that
unsafe network storage is a possible cause of this error. But I'm
a little worried that that'd be crying wolf, because on most setups
a much more likely explanation is somebody concurrently creating a
file in the targeted directory.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-01-08 20:44:00 | Re: improve DEBUG1 logging of parallel workers for CREATE INDEX? |
| Previous Message | Tom Lane | 2025-01-08 20:35:38 | Re: improve DEBUG1 logging of parallel workers for CREATE INDEX? |