Skip site navigation (1) Skip section navigation (2)

Re: Postgresql 'eats' all mi data partition

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Szepe <szepe(at)pinerecords(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>,Javier Carlos <fjcarlos(at)correo(dot)insp(dot)mx>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgresql 'eats' all mi data partition
Date: 2003-09-26 20:28:37
Message-ID: 27008.1064608117@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tomas Szepe <szepe(at)pinerecords(dot)com> writes:
> 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.

Okay, so a pkey index entry will take 32 bytes counting overhead ...
you've got about 10:1 bloat on the stats_min indexes and 2:1 in stats_hr.
Definitely bad :-(

I expect the bloat is coming from the fact that the interesting range of
"start" changes over time.  7.4 should be able to recycle index space
in that situation, but 7.3 and before can't.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2003-09-26 23:20:09
Subject: Re: [GENERAL] Can't Build 7.3.4 on OS X
Previous:From: Gaetano MendolaDate: 2003-09-26 20:10:26
Subject: Re: Postgresql 'eats' all mi data partition

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group