Re: precautions/prerequisites to take for specific table

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: precautions/prerequisites to take for specific table
Date: 2020-11-05 16:04:46
Message-ID: 49af972e-b140-2913-8723-01b20e1e20b6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/5/20 7:49 AM, Vasu Madhineni wrote:
> Hi All,
>
> In my organisation a newly built project application team requirement on
> tables like have a column (text type), with size can reach around 3 MB,
> and 45 million records annually.
>
> Are there any specific precautions/prerequisites we have to take from DBA
> end to handle this type of table.

Think about partitioning it by date.   Indexes will be smaller, and
archiving become trivial.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2020-11-05 16:12:56 Re: JSONB order?
Previous Message Tony Shelver 2020-11-05 15:45:51 Fwd: JSONB order?