Re: BUG #15950: pg_freespace.avail is 0 - Mailing list pgsql-bugs

From Jeff Janes
Subject Re: BUG #15950: pg_freespace.avail is 0
Date
Msg-id CAMkU=1wUADhJY_HE65tYDeUB6e1AeVxDjUL9Hk8VrFfmQj+ziA@mail.gmail.com
Whole thread Raw
In response to BUG #15950: pg_freespace.avail is 0  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Mon, Aug 12, 2019 at 2:08 PM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15950
Logged by:          Daniel Adeniji
Email address:      daniel_adeniji@hotmail.com
PostgreSQL version: 11.4
Operating system:   Windows 10
Description:       

Issued the query pasted below :-
...

Result :-
=========

1) pg_freespace.avail is 0

Your query didn't even return pg_freespace.avail.  It returned some convoluted thing that might depend on it.

Why is this a bug? Why is 0 wrong? What should it be instead?  If pg_freespace.avail is wrong, why not how a query that shows that, rather than something else tangentially related to it?  What is the actual output of the query you do show?

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose