From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Marcin Gozdalik <gozdal(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Changing locale of an existing database |
Date: | 2025-06-17 21:01:02 |
Message-ID: | c0bfdfbb-1f7a-4789-bcc6-5d2061b58c60@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/17/25 10:30, Marcin Gozdalik wrote:
> Around 100 DBs, ranging from 1TB to 50TB.
> Initial testing showed that it takes 1.5h to dump the DB and 3h to
> restore it for a DB of around 3TB.
>
> Just recreating the indexes takes around 30 minutes on the same DBs.
>
> I understand that pg_dump/pg_restore is the safe route but it's too slow
> for me so I'd like to understand if I have any alternative.
Alright I see the issue. I don't know enough about this to say whether
directly altering the system catalog would be a safe operation or not.
An answer to that is going to need to come from someone with more
knowledge on Postgres internals then I.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | vijay patil | 2025-06-18 17:12:30 | Request for Feedback on PostgreSQL HA + Load Balancing Architecture |
Previous Message | Masahiko Sawada | 2025-06-17 17:44:07 | Re: Logical Replication Memory Allocation Error - "invalid memory alloc request size" |