From: Scott Ribe <scott_ribe@elevated-dev.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Big image tables maintenance
Date: Mon, 17 Sep 2018 07:59:58 -0600
Message-ID: <0F8CB802-9FBC-4EA3-98AE-E81F26B3E559@elevated-dev.com> (raw)
In-Reply-To: <d056c4b6-30d5-25de-37cc-107a2382ae96@gmail.com>
References: <CAB3gP9JOKratDxJ54X+DR4axeK0k9ZO2wFw2_PiNovknCB8DsQ@mail.gmail.com>
<d056c4b6-30d5-25de-37cc-107a2382ae96@gmail.com>
On 09/17/2018 07:38 AM, still Learner wrote:
> Hi ,
>
> I have a 10 TB size table with multiple bytea columns (image & doc)and makes 20TB of DB size. I have a couple of issues to maintain the DB.
>
> 1. I Would like to separate the image column from the 10TB size table, place it in a separate schema. The change should not result in any query change in the application. Is it possible? Doing this it should not affect the performance.
They're automatically stored separate, see https://www.postgresql.org/docs/current/static/storage-toast.html.
> 2. I can't maintain files on File system as the count is huge,
So? I've stored millions of documents on a Mac mini. Real server hardware & OS should have no problem--10TB is really not all that much.
> so thinking of using any no-sql mostly mongo-DB, is it recommended? Or PostgreSQL itself can handle?
Only if all you need is the document storage, none of everything else PG offers.
> 3. Taking the backup of 20TB data, is big task. Any more feasible solution other than online backup/pg_dump?
That's an argument for keeping the presumably immutable files on the file system. (There are arguments against as well.)
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: scott_ribe@elevated-dev.com, pgsql-admin@lists.postgresql.org
Subject: Re: Big image tables maintenance
In-Reply-To: <0F8CB802-9FBC-4EA3-98AE-E81F26B3E559@elevated-dev.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