Thread: contrib/pg_freespacemap
Hi, Is there any reason we didn't move the pg_freespace function from contrib to core? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Is there any reason we didn't move the pg_freespace function from
> contrib to core?
Is there a reason we *should* move it? The current definition doesn't
leave me feeling that it's more than a low-level hacker's tool.
regards, tom lane
Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > > Is there any reason we didn't move the pg_freespace function from > > contrib to core? > > Is there a reason we *should* move it? The current definition doesn't > leave me feeling that it's more than a low-level hacker's tool. No specific reason. I was just wondering because I saw an old message about it. Maybe we just don't need it. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
On 8/8/09 10:50 AM, Alvaro Herrera wrote: > Tom Lane wrote: >> Alvaro Herrera <alvherre@commandprompt.com> writes: >>> Is there any reason we didn't move the pg_freespace function from >>> contrib to core? >> Is there a reason we *should* move it? The current definition doesn't >> leave me feeling that it's more than a low-level hacker's tool. > > No specific reason. I was just wondering because I saw an old message > about it. Maybe we just don't need it. Given that the FSM is now auto-managing, is there any reason to have this tool at all? Seems like it should get killed off. -- Josh Berkus PostgreSQL Experts Inc. www.pgexperts.com
Josh Berkus <josh@agliodbs.com> writes:
> Given that the FSM is now auto-managing, is there any reason to have
> this tool at all?
Maybe not, but I'd be inclined to wait a release or so until we have
more field experience with the new FSM. If, in a year, FSM is something
nobody worries about anymore, we can kill the contrib module.
regards, tom lane
On Aug 8, 2009, at 2:55 PM, Josh Berkus wrote: > On 8/8/09 10:50 AM, Alvaro Herrera wrote: >> Tom Lane wrote: >>> Alvaro Herrera <alvherre@commandprompt.com> writes: >>>> Is there any reason we didn't move the pg_freespace function from >>>> contrib to core? >>> Is there a reason we *should* move it? The current definition >>> doesn't >>> leave me feeling that it's more than a low-level hacker's tool. >> >> No specific reason. I was just wondering because I saw an old >> message >> about it. Maybe we just don't need it. > > Given that the FSM is now auto-managing, is there any reason to have > this tool at all? > > Seems like it should get killed off. I believe it's useful when dealing with very bloated relations. If someone's looking for an itch to scratch, ways to more effectively shrink bloated relations would be good. -- Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828