Re: Free space mapping (was Re: Multi-Versions and Vacuum)

From: Mark Kirkwood <markir(at)slingshot(dot)co(dot)nz>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>
Subject: Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Date: 2002-08-27 22:39:28
Message-ID: 3D6BFFA0.10906@slingshot.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

(mass snippage)
>The ever-growing tables
> that people are experiencing is somehow related to the new
> non-blocking vacuum and the value of the free space map settings...
>But if I understand now what you're saying, it's this: the vacuum
> _does_ get everything....

There is also a complicating effect when rows have toasted storage, which can prevent the space being freed (I think),
see hackers thread entitled something like "unbounded database growth".

I have set myself the task of examining this - but wish I had picked an easier 1st project :-(
- I am having to learn about vacuum, toasting ,freespace, and generally get to grips with the Pg code as well - just as well I have some free time at the moment...:-)

best wishes

Mark

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-08-27 22:45:05 Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Previous Message David Link 2002-08-27 22:14:02 Re: selecting multiple like-named columns