| From: | Harald Fuchs <hf0217x(at)protecting(dot)net> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: 12 hour table vacuums |
| Date: | 2007-10-24 09:04:27 |
| Message-ID: | pumyu8zxwk.fsf@srv.protecting.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
In article <471E26E4(dot)7040804(at)shaw(dot)ca>,
Ron St-Pierre <ron(dot)pgsql(at)shaw(dot)ca> writes:
>> For what it's worth NUMERIC columns take more space than you might expect.
>> Figure a minimum of 12 bytes your rows are at about 1.5k each even if the
>> non-numeric columns aren't large themselves. What are the other columns?
> The NUMERIC columns hold currency related values, with values ranging
> from a few cents to the billions, as well as a few negative numbers.
What's the required precision? If it's just cents (or maybe tenths
thereof), you could use BIGINT to store the amount in this precision.
This would give you exact values with much less space.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giulio Cesare Solaroli | 2007-10-24 10:44:35 | Finalizing commit taking very long |
| Previous Message | Alvaro Herrera | 2007-10-23 18:23:18 | Re: 12 hour table vacuums |