| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | Pgsql hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Strange issue with NFS mounted PGDATA on ugreen NAS |
| Date: | 2024-12-31 22:44:29 |
| Message-ID: | 4150172.1735685069@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 12/31/2024 12:22 pm, Larry Rosenman wrote:
>> When I try to drop a database, PostgreSQL leaves files in the directory
>> and does not even try to delete them.
>> PostgreSQL 16.6, FreeBSD 14.2, PGDATA mounted NFS from UGreen NAS.
FWIW, I couldn't reproduce such a problem with PG running on macOS
Sequoia and using an NFS mount from a RHEL8 machine. (I tried with
current master code, but I don't believe that we fixed any related
bugs recently.)
Can you try some other combinations of host OS and NFS source,
and see if you can identify what's needed to cause the failure?
What it looks like is that readdir() is skipping over some files,
which would almost certainly be an NFS server bug. But that
theory could be wrong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-12-31 23:06:59 | Adjusting hash join memory limit to handle batch explosion |
| Previous Message | Sami Imseih | 2024-12-31 21:35:02 | Re: add vacuum starttime columns |