Re: Compressed binary field - Mailing list pgsql-general

From Kevin Grittner
Subject Re: Compressed binary field
Date
Msg-id 504F35A4020000250004A1C7@gw.wicourts.gov
Whole thread Raw
In response to Re: Compressed binary field  (Edson Richter <edsonrichter@hotmail.com>)
Responses Re: Compressed binary field  (Edson Richter <edsonrichter@hotmail.com>)
List pgsql-general
Edson Richter <edsonrichter@hotmail.com> wrote:
> Em 11/09/2012 14:34, Kevin Grittner escreveu:
>> Edson Richter <edsonrichter@hotmail.com> wrote:
>>
>>> For storage, du -h --max-depth 1 on data directory gives me the
>>> amount of data.
>>
>>> Biggest objects are just the tables with files.
>>
>>> I've 2 tables that held all these objects. Structure is
>>>
>>> create table MYTABLE (id bigint not null primary key, mimetype
>>> varchar(100) null, bytea datafile null)
>>
>> Could you show the results of this query?:
>>
>> SELECT relkind, oid, relfilenode, reltoastrelid,
>>         relpages, reltuples
>>    FROM pg_class
>>    ORDER BY relpages DESC
>>    LIMIT 10;

> [biggest relation was a table heap with 29321 pages]

>> Also, just to be sure that all calculations are based on your
>> actual build, can you show the results of?:
>>
>> SHOW block_size;
> 8192

So your biggest table is actually 229 MB.  Something is not adding
up.  I can't see any way to reconcile your previous statements with
this number.  There also hasn't been any real explanation for the
statement that you have 250000 files.  There must be something which
matters here which hasn't yet been mentioned.  Any ideas?

-Kevin


pgsql-general by date:

Previous
From: Edson Richter
Date:
Subject: Re: Compressed binary field
Next
From: John R Pierce
Date:
Subject: Re: AIX and ipv6