| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Brent Wood <Brent(dot)Wood(at)niwa(dot)co(dot)nz>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Choosing an index on partitioned tables. |
| Date: | 2021-09-07 09:16:03 |
| Message-ID: | CABUevExw0Mvk1Rk2Fb8ciRG889-bjF5n_TgWAynY4JQbc3f2pw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 7, 2021 at 10:51 AM Tim Uckun <timuckun(at)gmail(dot)com> wrote:
>
> To be fair Timescale also adds some other features which might be
> useful. For example they add some SQL enhancements like last value
> and auto maintaining materialized views and such. The automatic
> management of partitions is also pretty big plus in my opinion. You
> can get some of the equivalent functionality by writing stored procs
> and deploying pg_cron but it's nice to have those things built in.
If you want automatic partition management, look at pg_partman. No
need to write your own procs and deploy with cron.
And FWIW, in reference to the discussions about AWS, it is supported on RDS.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2021-09-07 09:52:32 | Re: Choosing an index on partitioned tables. |
| Previous Message | Tim Uckun | 2021-09-07 08:51:00 | Re: Choosing an index on partitioned tables. |