From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Quan Zongliang <quanzongliang(at)yeah(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Available disk space per tablespace |
Date: | 2025-03-15 17:00:36 |
Message-ID: | Z9WyNDhDcXDUy4xD@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Thomas Munro
> > Hmm. Is looping on EINTR worth the trouble?
>
> I was just wondering if it might be one of those oddballs that ignores
> SA_RESTART, but I guess that doesn't seem too likely (I mean, first
> you'd probably have to have a reason to sleep or some other special
> reason, and who knows what some unusual file systems might do). It
> certainly doesn't on the systems I tried. So I guess not until we
> have other evidence.
Gnulib's get_fs_usage() (which is what GNU coreutil's df uses)
does not handle EINTR either.
There is some code that does int width expansion, but I believe we
don't need that since the `fst.f_bavail * fst.f_frsize` multiplication
takes care of converting that to int64 (if it wasn't already 64bits
before).
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2025-03-15 17:22:48 | Re: Update Unicode data to Unicode 16.0.0 |
Previous Message | Andres Freund | 2025-03-15 16:26:12 | Re: Changing the state of data checksums in a running cluster |