Search Postgresql Archives

Re: Large database design advice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Joe,

with a normal "serial", without "big", you can have 9.223.372.036.854.775.807 records individually numbered.

- Few tables but number of objects is tens-hundreds of thousands.
- less than 100 queries per second.

so you are talking about 10*100*1000=1000000 in words one million records? That is not very big.


Table: item
---------------------
account_id
item_id

So you have a combined primary key for item? That is technically totally correct, no problem.
Non the less I recommend to have a separate primary key column for item. As you are starting with databases, some things will be easier to do without having a combined key as primary.

How generally this design will hold up against this amount of data?

Insufficen data to parse "this amount" :) You did not give us any information about how WIDE your rows are. Some million records are nothing if there just hold social security numbers in them; they can get quite stressfull if every row carries 3 blobs containing Videos.

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Let's set so double the killer delete select all.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux