From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Mike Sofen <msofen@runbox.com>
To: pgsql-performance@postgresql.org
Subject: Re: Storing large documents - one table or partition by doc?
Date: Fri, 23 Sep 2016 13:59:42 -0500
Message-ID: <060e03cb-bd2b-beb9-b2a1-dc1bfd30b0ca@BlueTreble.com> (raw)
In-Reply-To: <042201d21594$0061acb0$01250610$@runbox.com>
References: <CACjtUOT+noY4RHt_qA6Jeb-2UD-2F-M=KDwPNS4KEnBL3BA87A@mail.gmail.com>
<042201d21594$0061acb0$01250610$@runbox.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, msofen@runbox.com
Subject: Re: Storing large documents - one table or partition by doc?
In-Reply-To: <060e03cb-bd2b-beb9-b2a1-dc1bfd30b0ca@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox