From: | Thomas Boussekey <thomas(dot)boussekey(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-General List <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Moving from Linux to Linux? |
Date: | 2025-03-11 20:49:05 |
Message-ID: | CALUeYmf1mfs1DDo0kuAZU+n5MeW4hN2AfVE1emDDsVJNu_+FJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le mar. 11 mars 2025 à 20:35, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> a
écrit :
> On Tue, Mar 11, 2025 at 2:35 PM Paul Foerster <paul(dot)foerster(at)gmail(dot)com>
> wrote:
>
>> Hi Devrim, Thomas, Adrian, Ron, Joe,
>>
>> answering to myself as answering to five postings in one go is
>> impossible. 🤣
>>
>> > Are there any obstacles that definitely make that a no-go? Do I risk
>> corruption? It's both Linux, just a different distribution.
>>
>> The question was a bit of an idea. So the glibc version in not known yet,
>> but I'm highly confident that they will differ. A reindex could in theory
>> be possible in most cases, but is a definite show stopper on some of our
>> databases, because it would mean too much application downtime.
>>
>> So, it's either logical replication or close to impossible.
>>
>
> If you don't do much DDL, the LR should be quite workable.
>
Stop DDL during the copy process is mandatory, but there are so other
restrictions to consider also (large objects, sequences...), see this page
for an exhaustive list:
https://www.postgresql.org/docs/current/logical-replication-restrictions.html
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
From | Date | Subject | |
---|---|---|---|
Next Message | Siraj G | 2025-03-12 01:48:29 | hide data from admins |
Previous Message | Adrian Klaver | 2025-03-11 20:24:37 | Re: Duplicate Key Values |