Re: [HACKERS] Improving free space usage (was: Reducing relation locking overhead)

2006-03-03 Thread Jim C. Nasby
At the risk of editorializing... * Allow for tables with more than a certain percent of free space to force new tuple allocation in the last few pages to come only from the FSM (prefering the earliest pages), with the intention of allowing the table to shrink I also believe there's also a s

Re: [HACKERS] Improving free space usage (was: Reducing relation locking overhead)

2006-03-02 Thread Bruce Momjian
Added to TODO: * Allow FSM to return free space toward the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM --- Jim C. Nasby wrote: > On Fri, Dec 09, 2005 at 12

Re: [HACKERS] Improving free space usage (was: Reducing relation locking overhead)

2005-12-08 Thread Jim C. Nasby
On Fri, Dec 09, 2005 at 12:00:14AM +0200, Hannu Krosing wrote: > > Along those lines, I've wondered if it makes sense to add more > > flexibility in how free space is reclaimed in a table. One obvious > > possibility is to have a strategy where new tuples will always look to > > the FSM for space (

[HACKERS] Improving free space usage (was: Reducing relation locking overhead)

2005-12-08 Thread Jim C. Nasby
On Thu, Dec 08, 2005 at 11:58:50AM +0200, Hannu Krosing wrote: > ??hel kenal p??eval, N, 2005-12-08 kell 01:08, kirjutas Jim C. Nasby: > > On Thu, Dec 08, 2005 at 08:57:42AM +0200, Hannu Krosing wrote: > > > ??hel kenal p??eval, N, 2005-12-08 kell 00:16, kirjutas Jim C. Nasby: > > > > On Sat, Dec 0