Re: Partitioning without downtime

From: ravi k <ravisql09(at)gmail(dot)com>
To: Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>
Cc: Loles <lolesft(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Partitioning without downtime
Date: 2022-04-22 16:42:49
Message-ID: CAFL4M8H1kmnx=NMmOk=rdV_31cE27JeSadwjm097NQKadyy9yw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

If you want update historical data while cutover it's difficult else you
can load historical data as chunks and then during switchover apply access
exclusive lock on table and load latest few hours data and rename table in
single transaction.

Best,
Ravindra

On Fri, 22 Apr, 2022, 9:08 pm Keith Fiske, <keith(dot)fiske(at)crunchydata(dot)com>
wrote:

>
>
> On Fri, Apr 22, 2022 at 11:28 AM Loles <lolesft(at)gmail(dot)com> wrote:
>
>> Hi!
>>
>> Is there a way to partition a table in production without downtime? Or
>> extension that allows it.
>>
>> Thanks!
>>
>
> Zero downtime (or without a table lock at some point) is not possible with
> native partitioning since you cannot convert an existing table into a
> natively partitioned table. However, it is possible to do it with very
> little downtime if the circumstances allow. I've laid out a method of doing
> this with pg_partman here -
> https://github.com/pgpartman/pg_partman/blob/master/doc/pg_partman_howto_native.md
>
> --
> Keith Fiske
> Senior Database Engineer
> Crunchy Data - http://crunchydata.com
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Sbob 2022-04-22 20:23:00 could not read block 0 in file Error
Previous Message Keith Fiske 2022-04-22 15:38:08 Re: Partitioning without downtime