public inbox for [email protected]help / color / mirror / Atom feed
Upgrade from 12.22 to 16 14+ messages / 9 participants [nested] [flat]
* Upgrade from 12.22 to 16 @ 2025-06-11 06:21 Wasim Devale <[email protected]> 0 siblings, 2 replies; 14+ messages in thread From: Wasim Devale @ 2025-06-11 06:21 UTC (permalink / raw) To: pgsql-admin; Pgsql-admin <[email protected]> Hi All Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart from in place upgrade. We have it on red hat 9. Thanks, Wasim ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 06:43 Laurenz Albe <[email protected]> parent: Wasim Devale <[email protected]> 1 sibling, 1 reply; 14+ messages in thread From: Laurenz Albe @ 2025-06-11 06:43 UTC (permalink / raw) To: Wasim Devale <[email protected]>; Pgsql-admin <[email protected]> On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote: > Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart > from in place upgrade. We have it on red hat 9. What do you mean with "apart from"? Yours, Laurenz Albe ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 06:53 Wasim Devale <[email protected]> parent: Laurenz Albe <[email protected]> 0 siblings, 3 replies; 14+ messages in thread From: Wasim Devale @ 2025-06-11 06:53 UTC (permalink / raw) To: Laurenz Albe <[email protected]>; +Cc: Pgsql-admin <[email protected]> I mean to say that we do not want to do the in place upgrade also the other option of taking dump and restoration of it. If I can have any robust plan who all have worked on that then please suggest me. Thanks, Wasim ---------- Forwarded message --------- From: Laurenz Albe <[email protected]> Date: Wed, 11 Jun, 2025, 12:13 pm Subject: Re: Upgrade from 12.22 to 16 To: Wasim Devale <[email protected]>, Pgsql-admin < [email protected]> On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote: > Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart > from in place upgrade. We have it on red hat 9. What do you mean with "apart from"? Yours, Laurenz Albe ^ permalink raw reply [nested|flat] 14+ messages in thread
* RE: Upgrade from 12.22 to 16 @ 2025-06-11 06:57 Domen Šetar <[email protected]> parent: Wasim Devale <[email protected]> 2 siblings, 1 reply; 14+ messages in thread From: Domen Šetar @ 2025-06-11 06:57 UTC (permalink / raw) To: Wasim Devale <[email protected]>; Laurenz Albe <[email protected]>; +Cc: Pgsql-admin <[email protected]> You can use logical replication if new version of your postgres is on other host. Best regards! [izum] Domen Šetar Computer Systems Support IZUM – Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/; | [email protected]<mailto:[email protected]> From: Wasim Devale <[email protected]> Sent: Wednesday, June 11, 2025 8:54 AM To: Laurenz Albe <[email protected]> Cc: Pgsql-admin <[email protected]> Subject: Re: Upgrade from 12.22 to 16 I mean to say that we do not want to do the in place upgrade also the other option of taking dump and restoration of it. If I can have any robust plan who all have worked on that then please suggest me. Thanks, Wasim ---------- Forwarded message --------- From: Laurenz Albe <[email protected]<mailto:[email protected]>> Date: Wed, 11 Jun, 2025, 12:13 pm Subject: Re: Upgrade from 12.22 to 16 To: Wasim Devale <[email protected]<mailto:[email protected]>>, Pgsql-admin <[email protected]<mailto:[email protected]>> On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote: > Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart > from in place upgrade. We have it on red hat 9. What do you mean with "apart from"? Yours, Laurenz Albe Attachments: [image/jpeg] image001.jpg (1.3K, 3-image001.jpg) download | view image ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 07:38 Laurenz Albe <[email protected]> parent: Wasim Devale <[email protected]> 2 siblings, 0 replies; 14+ messages in thread From: Laurenz Albe @ 2025-06-11 07:38 UTC (permalink / raw) To: Wasim Devale <[email protected]>; +Cc: Pgsql-admin <[email protected]> On Wed, 2025-06-11 at 12:23 +0530, Wasim Devale wrote: > > Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart > > from in place upgrade. We have it on red hat 9. > > I mean to say that we do not want to do the in place upgrade also the other option > of taking dump and restoration of it. If I can have any robust plan who all have > worked on that then please suggest me. "I want to upgrade with minimal downtime, but I don't want the natural, simple solution for upgrade with minimal downtime." Strange requirement, but if you feel you want to make your life more difficult, you can use logical replication for an upgrade with very short downtime. Yours, Laurenz Albe ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 13:38 Ron Johnson <[email protected]> parent: Wasim Devale <[email protected]> 2 siblings, 0 replies; 14+ messages in thread From: Ron Johnson @ 2025-06-11 13:38 UTC (permalink / raw) To: pgsql-admin On Wed, Jun 11, 2025 at 2:54 AM Wasim Devale <[email protected]> wrote: > I mean to say that we do not want to do the in place upgrade > Why not? Using the default --copy option, there's minimal downtime, and the old database is still there in case you need to fall back, etc. > also the other option of taking dump and restoration of it. If I can have > any robust plan who all have worked on that then please suggest me. > > Thanks, > Wasim > > ---------- Forwarded message --------- > From: Laurenz Albe <[email protected]> > Date: Wed, 11 Jun, 2025, 12:13 pm > Subject: Re: Upgrade from 12.22 to 16 > To: Wasim Devale <[email protected]>, Pgsql-admin < > [email protected]> > > > On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote: > > Please suggest me to upgrade postgresql: 400 GB data with minimal > downtime apart > > from in place upgrade. We have it on red hat 9. > > What do you mean with "apart from"? > > Yours, > Laurenz Albe > -- Death to <Redacted>, and butter sauce. Don't boil me, I'm still alive. <Redacted> lobster! ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 15:15 Zaid Shabbir <[email protected]> parent: Wasim Devale <[email protected]> 1 sibling, 0 replies; 14+ messages in thread From: Zaid Shabbir @ 2025-06-11 15:15 UTC (permalink / raw) To: Wasim Devale <[email protected]>; +Cc: pgsql-admin; Pgsql-admin <[email protected]> Hello Wasim, Minimum downtime can be achieved in a couple of ways, depending entirely on the specific requirements. If you're considering using logical replication to achieve this, the following article will definitely help you. https://www.pgedge.com/blog/always-online-or-bust-zero-downtime-major-version-postgres-upgrades Thanks & Regards Zaid On Wed, Jun 11, 2025 at 11:22 AM Wasim Devale <[email protected]> wrote: > Hi All > > Please suggest me to upgrade postgresql: 400 GB data with minimal downtime > apart from in place upgrade. We have it on red hat 9. > > Thanks, > Wasim > ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-11 15:29 Ron Johnson <[email protected]> parent: Domen Šetar <[email protected]> 0 siblings, 1 reply; 14+ messages in thread From: Ron Johnson @ 2025-06-11 15:29 UTC (permalink / raw) To: pgsql-admin On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]> 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! ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-14 14:53 Wasim Devale <[email protected]> parent: Ron Johnson <[email protected]> 0 siblings, 2 replies; 14+ messages in thread From: Wasim Devale @ 2025-06-14 14:53 UTC (permalink / raw) To: Ron Johnson <[email protected]>; +Cc: pgsql-admin; Pgsql-admin <[email protected]> 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, <[email protected]> wrote: > On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]> 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! > Attachments: [image/png] Screenshot_20250614-201825.png (355.8K, 3-Screenshot_20250614-201825.png) download | view image ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-14 19:49 Frank Lanitz <[email protected]> parent: Wasim Devale <[email protected]> 1 sibling, 0 replies; 14+ messages in thread From: Frank Lanitz @ 2025-06-14 19:49 UTC (permalink / raw) To: [email protected] Hi, On 14.06.25 16:53, Wasim Devale wrote: > Is there the restriction in logical replication because the database we > have has all of it shown in the screenshot. The manual is having a good list of restrictions. -> https://www.postgresql.org/docs/current/logical-replication-restrictions.html Cheers, Frank Attachments: [application/pgp-signature] OpenPGP_signature.asc (236B, 2-OpenPGP_signature.asc) download ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-16 04:43 DINESH NAIR <[email protected]> parent: Wasim Devale <[email protected]> 1 sibling, 1 reply; 14+ messages in thread From: DINESH NAIR @ 2025-06-16 04:43 UTC (permalink / raw) To: Wasim Devale <[email protected]>; Ron Johnson <[email protected]>; +Cc: pgsql-admin; Pgsql-admin <[email protected]> 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/media/img/about/press/elephant.png]<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. 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-ste... [https://media2.dev.to/dynamic/image/width=1000,height=500,fit=cover,gravity=auto,format=auto/https%3...]<https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-ste...; 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-ste...; 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 <[email protected]> Sent: Saturday, June 14, 2025 8:23 PM To: Ron Johnson <[email protected]> Cc: pgsql-admin <[email protected]>; Pgsql-admin <[email protected]> Subject: Re: Upgrade from 12.22 to 16 You don't often get email from [email protected]. 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, <[email protected]<mailto:[email protected]>> wrote: On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]<mailto:[email protected]>> 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! ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-16 18:10 Gaspare Boscarino, P.Eng. <[email protected]> parent: DINESH NAIR <[email protected]> 0 siblings, 1 reply; 14+ messages in thread From: Gaspare Boscarino, P.Eng. @ 2025-06-16 18:10 UTC (permalink / raw) To: DINESH NAIR <[email protected]>; +Cc: Wasim Devale <[email protected]>; Ron Johnson <[email protected]>; pgsql-admin; Pgsql-admin <[email protected]> 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 <[email protected]> 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. 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-ste... > > <https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-ste...; > 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-ste...; > 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 <[email protected]> > *Sent:* Saturday, June 14, 2025 8:23 PM > *To:* Ron Johnson <[email protected]> > *Cc:* pgsql-admin <[email protected]>; Pgsql-admin < > [email protected]> > *Subject:* Re: Upgrade from 12.22 to 16 > > You don't often get email from [email protected]. 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, <[email protected]> > wrote: > > On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]> 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 ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-16 18:12 David Okeamah <[email protected]> parent: Gaspare Boscarino, P.Eng. <[email protected]> 0 siblings, 1 reply; 14+ messages in thread From: David Okeamah @ 2025-06-16 18:12 UTC (permalink / raw) To: Gaspare Boscarino, P.Eng. <[email protected]>; DINESH NAIR <[email protected]>; +Cc: Wasim Devale <[email protected]>; Ron Johnson <[email protected]>; pgsql-admin; Pgsql-admin <[email protected]> Can you help out DAVID OKEAMAH,DEVELOPER ________________________________ From: Gaspare Boscarino, P.Eng. <[email protected]> Sent: Monday, June 16, 2025 7:10:22 PM To: DINESH NAIR <[email protected]> Cc: Wasim Devale <[email protected]>; Ron Johnson <[email protected]>; pgsql-admin <[email protected]>; Pgsql-admin <[email protected]> Subject: 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 <[email protected]<mailto:[email protected]>> 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/media/img/about/press/elephant.png]<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. Restrictions # Logical replication currently has the following restrictions or missing functionality. These might be addressed in future releases. The … www.postgresql.org<http://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-ste... [https://media2.dev.to/dynamic/image/width=1000,height=500,fit=cover,gravity=auto,format=auto/https%3...]<https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-ste...; 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-ste...; 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<http://dev.to; ________________________________ From: Wasim Devale <[email protected]<mailto:[email protected]>> Sent: Saturday, June 14, 2025 8:23 PM To: Ron Johnson <[email protected]<mailto:[email protected]>> Cc: pgsql-admin <[email protected]<mailto:[email protected]>>; Pgsql-admin <[email protected]<mailto:[email protected]>> Subject: Re: Upgrade from 12.22 to 16 You don't often get email from [email protected]<mailto:[email protected]>. 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, <[email protected]<mailto:[email protected]>> wrote: On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]<mailto:[email protected]>> 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<http://www.theoremasystems.com; | +1 604-765-0121 ^ permalink raw reply [nested|flat] 14+ messages in thread
* Re: Upgrade from 12.22 to 16 @ 2025-06-16 18:30 Gaspare Boscarino, P.Eng. <[email protected]> parent: David Okeamah <[email protected]> 0 siblings, 0 replies; 14+ messages in thread From: Gaspare Boscarino, P.Eng. @ 2025-06-16 18:30 UTC (permalink / raw) To: David Okeamah <[email protected]>; +Cc: DINESH NAIR <[email protected]>; Wasim Devale <[email protected]>; Ron Johnson <[email protected]>; pgsql-admin; Pgsql-admin <[email protected]> Hello David, I can help but I am not sure if this is the right channel for further communication. Thank you. Regards, Gaspare On Mon, Jun 16, 2025 at 11:12 AM David Okeamah <[email protected]> wrote: > Can you help out > > DAVID OKEAMAH,DEVELOPER > ------------------------------ > *From:* Gaspare Boscarino, P.Eng. <[email protected]> > *Sent:* Monday, June 16, 2025 7:10:22 PM > *To:* DINESH NAIR <[email protected]> > *Cc:* Wasim Devale <[email protected]>; Ron Johnson < > [email protected]>; pgsql-admin <[email protected]>; > Pgsql-admin <[email protected]> > *Subject:* 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 <[email protected]> > 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. 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-ste... > > <https://dev.to/raselmahmuddev/how-to-set-up-postgresql-logical-replication-use-cases-and-step-by-ste...; > 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-ste...; > 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 <[email protected]> > *Sent:* Saturday, June 14, 2025 8:23 PM > *To:* Ron Johnson <[email protected]> > *Cc:* pgsql-admin <[email protected]>; Pgsql-admin < > [email protected]> > *Subject:* Re: Upgrade from 12.22 to 16 > > You don't often get email from [email protected]. 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, <[email protected]> > wrote: > > On Wed, Jun 11, 2025 at 2:57 AM Domen Šetar <[email protected]> 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 > -- Gaspare Boscarino, P.Eng., M.Eng., MASc. Founder and CEO *Theorema Systems Inc.* www.theoremasystems.com | +1 604-765-0121 ^ permalink raw reply [nested|flat] 14+ messages in thread
end of thread, other threads:[~2025-06-16 18:30 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-06-11 06:21 Upgrade from 12.22 to 16 Wasim Devale <[email protected]> 2025-06-11 06:43 ` Laurenz Albe <[email protected]> 2025-06-11 06:53 ` Wasim Devale <[email protected]> 2025-06-11 06:57 ` Domen Šetar <[email protected]> 2025-06-11 15:29 ` Ron Johnson <[email protected]> 2025-06-14 14:53 ` Wasim Devale <[email protected]> 2025-06-14 19:49 ` Frank Lanitz <[email protected]> 2025-06-16 04:43 ` DINESH NAIR <[email protected]> 2025-06-16 18:10 ` Gaspare Boscarino, P.Eng. <[email protected]> 2025-06-16 18:12 ` David Okeamah <[email protected]> 2025-06-16 18:30 ` Gaspare Boscarino, P.Eng. <[email protected]> 2025-06-11 07:38 ` Laurenz Albe <[email protected]> 2025-06-11 13:38 ` Ron Johnson <[email protected]> 2025-06-11 15:15 ` Zaid Shabbir <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox