tag:blogger.com,1999:blog-4059581333784029364.post2544987631846080233..comments2022-03-25T02:12:24.460-07:00Comments on Coding and More - keeping track of annoying things I run into while coding: how to handle 400 Billion rows in postgressGert Wohlgemuthhttp://www.blogger.com/profile/02906619451323734545noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4059581333784029364.post-32752343986422060932013-07-23T03:30:23.853-07:002013-07-23T03:30:23.853-07:00I would be quite interested to see how large the i...I would be quite interested to see how large the indexes are. One reason partitioning a table speeds things up is because the indexes themselves are split. This means the index is more likely to fit into memory, updates/inserts will only affect a smaller index, etc.PGhttps://www.blogger.com/profile/05997883120856396412noreply@blogger.comtag:blogger.com,1999:blog-4059581333784029364.post-47676156416084207002013-01-12T14:59:47.158-08:002013-01-12T14:59:47.158-08:00Pretty much, at least in no decent way.Pretty much, at least in no decent way.Gert Wohlgemuthhttps://www.blogger.com/profile/02906619451323734545noreply@blogger.comtag:blogger.com,1999:blog-4059581333784029364.post-54172904006857226452013-01-09T12:35:52.223-08:002013-01-09T12:35:52.223-08:00so basically postgres can't handle more than 1...so basically postgres can't handle more than 1B rows, and you need to partition it at that point? Is there any other way?Roger Packhttps://www.blogger.com/profile/01578246846716577925noreply@blogger.com