SEO

#1 (**permalink**) 04-18-2008, 12:00 AM

On Fri, 2005-10-28 at 13:21 +1300, Mark Kirkwood wrote:

> regression=# SELECT c.relname, m.relblocknumber, m.blockfreebytes
> FROM pg_freespacemap m INNER JOIN pg_class c
> ON c.relfilenode = m.relfilenode LIMIT 10;
> relname | relblocknumber | blockfreebytes
> ------------------------+----------------+----------------
> sql_features | 5 | 2696
> sql_implementation_info | 0 | 7104
> sql_languages | 0 | 8016
> sql_packages | 0 | 7376
> sql_sizing | 0 | 6032
> pg_authid | 0 | 7424
> pg_toast_2618 | 13 | 4588
> pg_toast_2618 | 12 | 1680
> pg_toast_2618 | 10 | 1436
> pg_toast_2618 | 7 | 1136
> (10 rows)
>
> [I found being able to display the FSM pretty cool, even if I say so
> myself....].

I like this, but not because I want to read it myself, but because I
want to make autovacuum responsible for re-allocating free space when it
runs out. This way we can have an autoFSM feature in 8.2

Best Regards, Simon Riggs

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

#2 (**permalink**) 04-18-2008, 12:00 AM

Simon Riggs wrote:
> On Fri, 2005-10-28 at 13:21 +1300, Mark Kirkwood wrote:
>
> > regression=# SELECT c.relname, m.relblocknumber, m.blockfreebytes
> > FROM pg_freespacemap m INNER JOIN pg_class c
> > ON c.relfilenode = m.relfilenode LIMIT 10;
>
>
> I like this, but not because I want to read it myself, but because I
> want to make autovacuum responsible for re-allocating free space when it
> runs out. This way we can have an autoFSM feature in 8.2

What do you mean, re-allocating free space? I don't understand what you
are proposing.

--
Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"Use it up, wear it out, make it do, or do without"

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#3 (**permalink**) 04-18-2008, 12:00 AM

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Simon Riggs wrote:
>> I like this, but not because I want to read it myself, but because I
>> want to make autovacuum responsible for re-allocating free space when it
>> runs out. This way we can have an autoFSM feature in 8.2

> What do you mean, re-allocating free space? I don't understand what you
> are proposing.

And even less why autovacuum would go through a view to get at the info.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#4 (**permalink**) 04-18-2008, 12:03 AM

Simon Riggs wrote:
>
>
> I like this, but not because I want to read it myself, but because I
> want to make autovacuum responsible for re-allocating free space when it
> runs out. This way we can have an autoFSM feature in 8.2
>
>

Not wanting to denigrate value of the interesting but slightly OT
direction this thread has taken - but does anybody want to
comment/review the patch itself :-) ....?

Cheers

Mark

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#5 (**permalink**) 04-18-2008, 12:04 AM

Mark Kirkwood wrote:
> Simon Riggs wrote:
> >
> >
> > I like this, but not because I want to read it myself, but because I
> > want to make autovacuum responsible for re-allocating free space when it
> > runs out. This way we can have an autoFSM feature in 8.2
> >
> >
>
> Not wanting to denigrate value of the interesting but slightly OT
> direction this thread has taken - but does anybody want to
> comment/review the patch itself :-) ....?

I saw this question about a transaction block and your reply:

http://archives.postgresql.org/pgsql...0/msg00226.php

but no new patch. I know someone suggested pgfoundry but it seems most
natural in /contrib. Do you want to update the patch?

--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#6 (**permalink**) 04-18-2008, 12:04 AM

Bruce Momjian wrote:
> Mark Kirkwood wrote:
>
>>Simon Riggs wrote:
>>
>>>
>>>I like this, but not because I want to read it myself, but because I
>>>want to make autovacuum responsible for re-allocating free space when it
>>>runs out. This way we can have an autoFSM feature in 8.2
>>>
>>>
>>
>>Not wanting to denigrate value of the interesting but slightly OT
>>direction this thread has taken - but does anybody want to
>>comment/review the patch itself :-) ....?
>
>
> I saw this question about a transaction block and your reply:
>
> http://archives.postgresql.org/pgsql...0/msg00226.php
>
> but no new patch. I know someone suggested pgfoundry but it seems most
> natural in /contrib. Do you want to update the patch?
>

In the expectation of further revisions, I was going to batch that one
in with the 'rest' - given that there have not been any, I'll submit a
revised patch.

Cheers

Mark

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: TODO Item - Add system view to show free space map