| From: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | Anjul Tyagi <anjul(at)ibosstech-us(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Table Partitioning |
| Date: | 2021-01-19 13:32:34 |
| Message-ID: | CAODZiv6HQSSMKFR-L4_GP8dRmOdp1mRC9WjG2nicUTE=u0z6=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Jan 19, 2021 at 7:12 AM hubert depesz lubaczewski <depesz(at)depesz(dot)com>
wrote:
> On Tue, Jan 19, 2021 at 12:01:12PM +0000, Anjul Tyagi wrote:
> > Can we handle that in DB side with trigger?
>
> I don't think so. At least not easily.
>
> You could make a function to do so, though.
>
> Best regards,
>
> depesz
>
>
>
>
As depesz said, a trigger is possible, but very tricky. I was never able to
find a good trigger-based, solution to these kinds of updates for
pg_partman myself. Thankfully support for updates that move data between
child tables was added for native partitioning in PG11. I would highly
suggest planning an upgrade to your major version of PG. Skip 11 and go
right to 12 or 13. An upgrade would be arguably easier than trying to code
this yourself. And the added features to native partitioning in 11 and
above will make managing them far better in the long run.
--
Keith Fiske
Senior Database Engineer
Crunchy Data - http://crunchydata.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Graham Everton | 2021-01-19 15:00:41 | Re: Table Partitioning |
| Previous Message | hubert depesz lubaczewski | 2021-01-19 12:12:04 | Re: Table Partitioning |