Re: Postgresql 'eats' all mi data partition - Mailing list pgsql-bugs

From Tomas Szepe
Subject Re: Postgresql 'eats' all mi data partition
Date
Msg-id 20030926193537.GB27274@louise.pinerecords.com
Whole thread Raw
In response to Re: Postgresql 'eats' all mi data partition  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgresql 'eats' all mi data partition  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> [tgl@sss.pgh.pa.us]
>
> You've definitely got an index-bloat problem on stats_min (the indexes
> are four times the size of the table :-(), and I suspect the same on
> stats_hr, though not quite as bad.  What are the datatypes of the
> index columns?

indexes:
stats_min_pkey primary key btree (ip, "start")
stats_min_start btree ("start")
stats_hr_pkey primary key btree (ip, "start")
stats_hr_start btree ("start")

ip is of type "inet" in all tables.
start is of type "timestamp without time zone" in all tables.

> > Hmm, you seem to suggest that we might expect a change in this regard
> > as 7.4 ships.  Is that right?
>
> 7.4 should improve matters.

Trouble is, I probably can't give it a try on the production machine
unless I'm sure it won't trash the data, and I don't know of a way to
reproduce the workload on a test setup. :(

Thanks,
--
Tomas Szepe <szepe@pinerecords.com>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgresql 'eats' all mi data partition
Next
From: Gaetano Mendola
Date:
Subject: Re: Postgresql 'eats' all mi data partition