Feedback-ID: i76984098:Fastmail
Message-ID: <c0bfdfbb-1f7a-4789-bcc6-5d2061b58c60@aklaver.com>
Date: Tue, 17 Jun 2025 14:01:02 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Changing locale of an existing database
To: Marcin Gozdalik <gozdal@gmail.com>
Cc: pgsql-general@postgresql.org
References: <CADu1mRP=rTC2WX=-EWqCX-CWjp9q09xxuEkK=2Se3wx1HasSkQ@mail.gmail.com>
 <603f35e6-32b2-4044-bbfb-5e70bba5164b@aklaver.com>
 <CADu1mROP5-zURekH1gF69W3Hz3pteryM=8T4-VJWM3shKM9mKQ@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CADu1mROP5-zURekH1gF69W3Hz3pteryM=8T4-VJWM3shKM9mKQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/c0bfdfbb-1f7a-4789-bcc6-5d2061b58c60%40aklaver.com>
Precedence: bulk

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.klaver@aklaver.com