| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | daniel_adeniji(at)hotmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15950: pg_freespace.avail is 0 |
| Date: | 2019-08-12 20:38:04 |
| Message-ID: | CAMkU=1wUADhJY_HE65tYDeUB6e1AeVxDjUL9Hk8VrFfmQj+ziA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Aug 12, 2019 at 2:08 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15950
> Logged by: Daniel Adeniji
> Email address: daniel_adeniji(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2019-08-12 22:25:02 | Re: BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose |
| Previous Message | PG Bug reporting form | 2019-08-12 20:22:58 | BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose |