pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Anjul Tyagi <anjul@ibosstech-us.com>
To: Amit jain <amit7.jain@gmail.com>
To: Keith Fiske <keith.fiske@crunchydata.com>
Cc: depesz@depesz.com, pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Table Partitioning
Date: Wed, 20 Jan 2021 04:58:11 +0000
Message-ID: <em49306724-d3b0-40e7-ac2f-fd07dcb60e9b@iboss01108> (raw)
In-Reply-To: <CAFBajrNcYX97E5S6cN2t_OaDz43o77s7Q0J7xj8THQS9a9T3pQ@mail.gmail.com>
References: <em77ea4711-7a8c-4eae-a935-4136d303ea88@iboss01108>
	<20210119114246.GA13372@depesz.com>
	<em953b223e-5ce1-4b39-a943-f101af602baa@iboss01108>
	<20210119121204.GB13372@depesz.com>
	<CAODZiv6HQSSMKFR-L4_GP8dRmOdp1mRC9WjG2nicUTE=u0z6=A@mail.gmail.com>
	<CAFBajrNcYX97E5S6cN2t_OaDz43o77s7Q0J7xj8THQS9a9T3pQ@mail.gmail.com>

Thanks Amit and Keith for your advise.




Regards,

Anjul TYAGI



ΓΌ Go Green


------ Original Message ------
From: "Amit jain" <amit7.jain@gmail.com>
To: "Keith Fiske" <keith.fiske@crunchydata.com>
Cc: depesz@depesz.com; "Anjul Tyagi" <anjul@ibosstech-us.com>; 
"pgsql-admin" <pgsql-admin@postgresql.org>
Sent: 1/19/2021 8:45:31 PM
Subject: Re: Table Partitioning

>I am totally agree with Keith opinion on better to go Upgrade rather 
>than managing partitioning code.
>
>Even PG version 11 has lot of partitioning features over older one, was 
>written a blog on same, can have a glance.
>https://severalnines.com/database-blog/how-take-advantage-new-partitioning-features-postgresql-11
>
>
>On Tue, Jan 19, 2021 at 7:03 PM Keith Fiske 
><keith.fiske@crunchydata.com> wrote:
>>
>>
>>On Tue, Jan 19, 2021 at 7:12 AM hubert depesz lubaczewski 
>><depesz@depesz.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

view thread (14+ messages)

Message-ID: <em49306724-d3b0-40e7-ac2f-fd07dcb60e9b@iboss01108>
Permalink:  ../em49306724-d3b0-40e7-ac2f-fd07dcb60e9b@iboss01108/
Also on:    postgresql.org/message-id/em49306724-d3b0-40e7-ac2f-fd07dcb60e9b@iboss01108

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: anjul@ibosstech-us.com, amit7.jain@gmail.com, keith.fiske@crunchydata.com
  Subject: Re: Table Partitioning
  In-Reply-To: <em49306724-d3b0-40e7-ac2f-fd07dcb60e9b@iboss01108>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox