Re: Database Bloat

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database Bloat
Date: 2012-08-20 19:33:26
Message-ID: 50329106.9070901@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/20/12 11:46 AM, elliott wrote:
> envdb=# \d astgtm2_n60e073;
> Table "public.astgtm2_n60e073"
> Column | Type | Modifiers
> --------+---------+-----------
> lat | real |
> lon | real |
> alt | integer |
> Indexes:
> "q3c_astgtm2_n60e073_idx" btree (q3c_ang2ipix(lon, lat)) CLUSTER

so, you DO have an index. what type does this function
q3c_ang2ipix(real,real) return ? googling it suggested a bigint, which
means every 12 byte (real,real,int) row has a corresponding b-tree entry
of 8 bytes plus b-tree stuff. I see you used cluster on this, did you
do the CLUSTER after populating the table, and before checking the
pg_total_relation_size that you reported as 20X your data ?

--
john r pierce N 37, W 122
santa cruz ca mid-left coast

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hermano Cabral 2012-08-20 19:59:25 .Net/C# - How to use Entity Framework Code First with Npgsql?
Previous Message Martijn van Oosterhout 2012-08-20 19:06:01 Re: How hard would a "path" operator be to implement in PostgreSQL