On 9/23/16 7:14 AM, Mike Sofen wrote:
So with proper indexing, I can’t see where there will be a performance issue.
Table bloat could become problematic. If there is a pattern where you can predict which documents are likely to be active (say, documents that have been modified in the last 10 days), then you can keep all of those in a set of tables that is fairly small, and keep the remaining documents in a set of "archive" tables. That will help reduce bloat in the large archive tables. Before putting in that extra work though, I'd just try the simple solution and see how well it works.
-- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
