Re: Upgrade from 12.22 to 16

Hello Wasim,

I suggest the logical replication approach. As mentioned before in this
thread, there are some limitations like DDL propagation, the need for
primary keys, etc. However, those constraints are not problematic and if
planned properly the result is excellent. I have used logical replication
many times for databases with TB of data.

Thank you.

Regards,

Gaspare

On Sun, Jun 15, 2025 at 9:43 PM DINESH NAIR <Dinesh_Nair(at)iitmpravartak(dot)net>
wrote:

> Hope this below mentionsed on the restrictions to be useful on the
> database schema and DDL commands are not replicated
>
>
> https://www.postgresql.org/docs/current/logical-replication-restrictions.html
>
> <https://www.postgresql.org/docs/current/logical-replication-restrictions.html>
> PostgreSQL: Documentation: 17: 29.7. Restrictions
> <https://www.postgresql.org/docs/current/logical-replication-restrictions.html>
> 29.7.&nbsp;Restrictions # Logical replication currently has the following
> restrictions or missing functionality. These might be addressed in future
> releases. The …
> www.postgresql.org
> Another useful link on enabling replication
>
>
> https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-step-guide-536b
>
> <https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-step-guide-536b>
> How to Set Up PostgreSQL Logical Replication: Use Cases and Step-by-Step
> Guide.
> <https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-step-guide-536b>
> Real-World Use Case 2: E-commerce Platforms Use Case: An e-commerce
> platform uses logical replication to keep the data in sync between the main
> database (handling customer transactions) and a separate reporting database
> (used for analytics).This ensures that the system can generate real-time
> reports and insights without affecting the performance of the website or
> app.
> dev.to
>
>
>
>
> ------------------------------
> *From:* Wasim Devale <wasimd60(at)gmail(dot)com>
> *Sent:* Saturday, June 14, 2025 8:23 PM
> *To:* Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> *Cc:* pgsql-admin <pgsql-admin(at)postgresql(dot)org>; Pgsql-admin <
> pgsql-admin(at)lists(dot)postgresql(dot)org>
> *Subject:* Re: Upgrade from 12.22 to 16
>
> You don't often get email from wasimd60(at)gmail(dot)com(dot) Learn why this is
> important <https://aka.ms/LearnAboutSenderIdentification>
> Caution: This email was sent from an external source. Please verify the
> sender’s identity before clicking links or opening attachments.
>
> Thanks everyone.
>
> Is there the restriction in logical replication because the database we
> have has all of it shown in the screenshot.
>
>
> On Wed, 11 Jun, 2025, 8:59 pm Ron Johnson, <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>
> On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <domen(dot)setar(at)izum(dot)si> wrote:
>
> You can use logical replication if new version of your postgres is on
> other host.
>
>
> Are you sure? There _shouldn't_ be any problem with replicating to a new
> instance on the same machine.
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
>

--
Gaspare Boscarino, P.Eng., M.Eng., MASc.
Founder and CEO
*Theorema Systems Inc.*
www.theoremasystems.com | +1 604-765-0121