Postgres Pro
Downloads
Home   >   mailing lists

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

From Daniel Adeniji
Subject Re: BUG #15950: pg_freespace.avail is 0
Date
Msg-id BYAPR20MB245699680361330B8D0961BEFFD20@BYAPR20MB2456.namprd20.prod.outlook.com
Whole thread Raw
In response to BUG #15950: pg_freespace.avail is 0  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view
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


Best,

Daniel Adeniji

From: Daniel Adeniji <daniel_adeniji@hotmail.com>
Sent: Monday, August 12, 2019 2:04 PM
To: Jeff Janes <jeff.janes@gmail.com>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.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


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.janes@gmail.com>
Sent: Monday, August 12, 2019 1:38 PM
To: daniel_adeniji@hotmail.com <daniel_adeniji@hotmail.com>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15950: pg_freespace.avail is 0
 
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: Thomas Munro
Date:
Subject: Re: BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose
Next
From: "两个孩子的爹"
Date:
Subject: 回复： BUG #15949: pg_basebackup failed(PG-12-Beta3)