Re: BUG #15950: pg_freespace.avail is 0

Jeff :-

Sorry that I did not provide ore information.

I was hoping the issue will be easy to re-create.

Here are the steps to re create :-

1. I Created a table
2. Added records to it
3. Updated and deleted records, hoping to create free pages

I have documented same here :-

PostgreSQL :- Create free pages in Table
https://learningintheopen.org/2019/08/12/postgresql-create-freepages-in-table/.

Best,

Daniel Adeniji

________________________________
From: Daniel Adeniji <daniel_adeniji(at)hotmail(dot)com>
Sent: Monday, August 12, 2019 2:04 PM
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15950: pg_freespace.avail is 0

Jeff :-

Sorry :-

Here are the steps to re create :-

1. I Created a table
2. Added records to it
3. Updated and deleted records, hoping to create free pages

I have documented same here.

PostgreSQL :- Create free pages in Table
https://learningintheopen.org/2019/08/12/postgresql-create-freepages-in-table/

Sorry it is my first time creating a bug/issue and I am not really used to the forum.

Best,

Daniel Adeniji

________________________________
From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Sent: Monday, August 12, 2019 1:38 PM
To: daniel_adeniji(at)hotmail(dot)com <daniel_adeniji(at)hotmail(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15950: pg_freespace.avail is 0

On Mon, Aug 12, 2019 at 2:08 PM PG Bug reporting form <noreply(at)postgresql(dot)org<mailto: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<mailto: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