| From: | Philip Semanchuk <philip(at)americanefficient(dot)com> |
|---|---|
| To: | Vasu Madhineni <vasumdba1515(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: precautions/prerequisites to take for specific table |
| Date: | 2020-11-05 15:05:32 |
| Message-ID: | C4564A3D-7B86-466F-8F26-B6D87D166BB8@americanefficient.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Nov 5, 2020, at 8:49 AM, Vasu Madhineni <vasumdba1515(at)gmail(dot)com> 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.
Hi Vasu,
Postgres can handle that just fine. We have a table with two text columns that’s 18Gb and almost 400 million rows, and that’s not a big table by some people’s standards.
If you have specific concerns, you’ll need to tell us more about your situation and why you think you won’t be satisfied.
Cheers
Philip
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Shelver | 2020-11-05 15:34:51 | JSONB order? |
| Previous Message | Adrian Klaver | 2020-11-05 14:58:11 | Re: greater than vs between in where clause |