From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: moving from MySQL to pgsql |
Date: | 2012-10-13 23:53:06 |
Message-ID: | k5cut2$rst$1@reversiblemaps.ath.cx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2012-10-13, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Sat, Oct 13, 2012 at 3:22 AM, Jasen Betts <jasen(at)xnet(dot)co(dot)nz> wrote:
>> On 2012-10-11, Vineet Deodhar <vineet(dot)deodhar(at)gmail(dot)com> wrote:
>>
>>> To give an example, I have tables for storing master records (year master,
>>> security master, etc.) for which pkid TINYINT is just sufficient.
>>> These pkid's are used as fk constraints in tables for storing business
>>> transactions.
>>> The no. of rows in business transactions tables is in millions.
>>> Here, I NEED to worry about the storage space occupied by the pkid fields.
>>
>> with disk at about 50c/Gigabyte why is it you need to worry?
>
> see upthread: OP is running off a USB stick. If he's running MyISAM,
> the postgres database is going to be larger and there is going to be a
> lot more writing than he's used to.
>
So, $5/gigabyte, and shorter life than disk, I can see how that could
start to hurt if you need to deploy a thousand.
--
⚂⚃ 100% natural
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2012-10-13 23:56:23 | Re: Postgres DB Migration from 8.3 to 9.1 |
Previous Message | Vibhor Kumar | 2012-10-13 23:31:37 | Re: citext question |