| From: | Andrei Zhidenkov <andrei(dot)zhidenkov(at)n26(dot)com> |
|---|---|
| To: | Ravi Krishna <srkrishna(at)myself(dot)com> |
| Cc: | Vikas Sharma <shavikas(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Partitioning large table (140GB) |
| Date: | 2019-11-20 10:51:09 |
| Message-ID: | 87B2C428-2932-47BA-B1A6-7A68986D3DA9@n26.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
You can also use extensions like pg_partman or pg_pathman. The last one allows to partition tables smoothly on live environments.
> On 20. Nov 2019, at 11:49, Ravi Krishna <srkrishna(at)myself(dot)com> wrote:
>
>> In our production, we use postgres 9.5 with streaming replication
>> using repmgr, there is a large table of 140GB size which receives
>> lots of inserts,
>> Is it possible to partition this table in this version of postgres?
>> and if so, please, can someone let me know the best way to accomplish
>> this and the best practices around it?
>
> In this version only inheritance is possible. From my experience avoid using
> triggers for insert and let the application (if possible) directly write to the
> right table.
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soto Cuevas Manuel Alejandro | 2019-11-20 12:12:21 | Re: PostGreSQL Replication and question on maintenance |
| Previous Message | Ravi Krishna | 2019-11-20 10:49:19 | Re: Partitioning large table (140GB) |