Re: table size/record limit
От | Gaetano Mendola |
---|---|
Тема | Re: table size/record limit |
Дата | |
Msg-id | 4178B88B.3030604@bigfoot.com обсуждение исходный текст |
Ответ на | table size/record limit (Dennis Gearon <gearond@fireserve.net>) |
Ответы |
Re: table size/record limit
|
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dennis Gearon wrote: | Gaetano Mendola wrote: | |> Dennis Gearon wrote: |> |>> I am designing something that may be the size of yahoo, google, ebay, |>> etc. |>> |>> Just ONE many to many table could possibly have the following |>> characteristics: |>> |>> 3,600,000,000 records |> |> This is a really huge monster one, and if you don't partition that |> table in some way I think you'll have nightmares with it... |> |> Regards |> Gaetano Mendola |> | thanks for the input, Gaetano. For partion in some way I don't mean only split it in more tables. You can use some available tools in postgres and continue to see this table as one but implemented behind the scenes with more tables. One usefull and impressive way is to use the inheritance in order to obtain a vertical partition 0) Decide a partition policy ( based on time stamp for example ) 1) Create an empty base table with the name that you want see as "public" 2) Create the partition using the empty table as base table 3) Create a rule on the base table so an insert or the update on it is ~ performed as a insert or an update on the right table ( using the partition ~ policy at step 0 ) in this way you are able to vacuum each partition, reindex each partition and so on in a more "feseable way" I do not immagine vacuum full or reindex a 3,600,000,000 records table... Regards Gaetano Mendola -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBeLiK7UpzwH2SGd4RAh+TAJ4w89SvkFWgt9DGhQx/aUR6j2wDtwCgtut5 FN0OuoycbI37a8Wouvo3icw= =Wb6h -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: