Re: Daniel Gustafsson 2019-11-12 <[hidden email]>
> I agree with Tomas upthread that it's unclear whether this needs to be in core.
> There are many system parameters a database admin is likely to be interested
> in, diskspace being just one of them (albeit a very important one for many
> reasons), and there is nothing that makes the SQL interface (or postgres core
> for that matter) particularly more suited for this job than other existing
> Why is SQL level crucial for this?
Because the figure is interesting to users as well. They will usually
not have any access to monitoring, and checking if they can load this
extra 10 GB dataset is a good use case.
This is about providing the numbers in the place where they are
needed. Of course admins can just go elsewhere to look it up (and
probably will), but I think now there's a usability gap for people who
just have SQL access.
On Tue, Nov 12, 2019 at 2:48 AM Michael Paquier <[hidden email]> wrote:
> On Mon, Nov 11, 2019 at 09:11:35PM +0100, Laurenz Albe wrote:
> > Will this work on Windows?
> > A quick web search seems to indicate that Windows has no statfs(2).
> It won't. We are actually discussing the compatibility aspects and
> the minimal data set we could grab in a different part of the thread.
For the record I already mentioned Windows specificity in  and
GetDiskFreeSpaceA  looks like the function to use on windows.