Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uPg8o-00DDCU-IX for pgsql-admin@arkaria.postgresql.org; Thu, 12 Jun 2025 11:30:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uPg8m-00BhQ2-Lv for pgsql-admin@arkaria.postgresql.org; Thu, 12 Jun 2025 11:30:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uPJ6r-002Bnc-Mq for pgsql-admin@lists.postgresql.org; Wed, 11 Jun 2025 10:55:10 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uPJ6q-001PyV-2B for pgsql-admin@lists.postgresql.org; Wed, 11 Jun 2025 10:55:09 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2ea080f900cso1197264fac.2 for ; Wed, 11 Jun 2025 03:55:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749639306; x=1750244106; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=bD/rtHqmrwRPyAWLhLGAJjDnSIzk+x43tyUjCSiYInQ=; b=X98M7h66GGHq9Y4VPozFTuzP2Ihqu0wIDTKqo5a6os0b7Cz8a4FD/yK5GJFO6LFKPT e8Qb+iGmMgyvJuHYke5hU4HehpEyEPmAMDyhX602edd9ovpw+QyZVnlaaVhR86CMG2Jc EumLPVK4iq4H/Q7Q2+wxO0bWNX86e+KVPlDh9Q0wrCReXFYv7/6ifGoU8xBNhlNg3P/C saEgTHcWI51ksk4n1SKdIxBQMHg284fJCcUNickKj+kx6dUXZi4xnZSr1mDDgrfbBiJo wYmbMYFcJVqguJnOiUgJUzZYsTy+g8yEJyQuR+m2efQFDJBQXW+2wmKGaWLgjocIatAa SUOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749639306; x=1750244106; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bD/rtHqmrwRPyAWLhLGAJjDnSIzk+x43tyUjCSiYInQ=; b=uS2/l+0RF/1PEFBqsbHs5qY5DyFPXNSa5LnH+y66uajlc4sOkc0YB6K84wHOKBlJme IAng4KGgYV/sqSrwLyHbEmMHKWFQ4qn7veS5nt069Oz/CE3sV3NJuEEPzByfSM4SINv9 lwrmqU1W/saHl7qetifnrkEb2u3MMPICVgcIKGmx7ACR2pJtOPfunZokDwc+gumMfjbc 1pN1gtqMNMQJgSDSkCTu2PAUZZ+zRBe8xWIS/kdu8Md3g8V8d6lpexM9vrzySwR6jCUb nRaTbqg0Qvqu++ssal94YKHAoa+YgEsy9BxvBfXb7FCk/FePb0TosRRvEDuI8pkjK93H sJmA== X-Gm-Message-State: AOJu0YwOT8DCNgWTOfwGOWj58iagdyUh533GXyY+HBay+TI+0I49Lm4F BTjFwHbO4oTZ48ir7pqMAY7YJVD5e2ahqT/mGqV+pWddSjIlQfIWKJSUj6jQ8gdAGxo10+0uBrb KKEax5XTcUy//XD5+LLmsUZ8Hh+up7BsKS76L X-Gm-Gg: ASbGncuf/oCK5Q2Ab6WEvBqRfd7lgtLnHr2yHaBSG2tJez+2RXrjins/zMRXUfRkjib t2bp4HXZ8mjndTKM76BlHDuI6D6v/mjfrxzl27fIlAKsIyDVhrTA2zlaHeiUUfz9B1t2a5IWUh/ +qq57ZctjWOBvlxsjG1f5e2BZGca7pcEEN9xpHIARlvrO/ X-Google-Smtp-Source: AGHT+IHoW//k0sSij1+2O/3hvMT4TyTyvlpugyYtw2yAn3J/ZOd4hXL91kuFjNuxwX89fXplUAWmVvRaOX+8zUfQZAI= X-Received: by 2002:a05:6871:6c09:b0:2d6:6677:f311 with SMTP id 586e51a60fabf-2ea9969417dmr1287296fac.3.1749639306032; Wed, 11 Jun 2025 03:55:06 -0700 (PDT) MIME-Version: 1.0 From: Kushal Shri Date: Wed, 11 Jun 2025 16:39:54 +0545 X-Gm-Features: AX0GCFvtAAm3wI-2XSgwyrfpuO3LA_85zzqzqMouM-eEkyOC-uUDRbdjyeGHIk8 Message-ID: Subject: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000523b12063749a5c6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000523b12063749a5c6 Content-Type: text/plain; charset="UTF-8" Dear Community, We are in the process of planning a PostgreSQL upgrade and would greatly appreciate any insights, best practices, or lessons learned from your experiences. Current Setup: - PostgreSQL version: 9.5 - Django version: 2.0 - Database size: ~3 TB - One Master 4 Replicas(Streaming Replication) We are taking a phased approach to this upgrade. In Phase 1, our goal is to upgrade PostgreSQL from v9.5 to v12, ensuring compatibility with our current Django 2.0 application. As part of this, I would like to understand: - What is the highest PostgreSQL version reliably supported with Django 2.0? - What upgrade strategies or methods have worked well for you in similar environments? - Any gotchas or performance considerations to keep in mind with large databases during such upgrades? Your recommendations and experiences will be extremely valuable in helping us plan and execute this upgrade smoothly. Thank you in advance for your support! --000000000000523b12063749a5c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Community,

We are in the process of planning a= PostgreSQL upgrade and would greatly appreciate any insights, best practic= es, or lessons learned from your experiences.

Current Setup:
=C2= =A0 =C2=A0- PostgreSQL version: 9.5
=C2=A0 =C2=A0- Django version: 2.0=C2=A0 =C2=A0- Database size: ~3 TB
=C2=A0 =C2=A0- One Master 4 Replic= as(Streaming Replication)

We are taking a phased approach to this up= grade. In Phase 1, our goal is to upgrade PostgreSQL from v9.5 to v12, ensu= ring compatibility with our current Django 2.0 application.

As part = of this, I would like to understand:

- What is the highest PostgreSQ= L version reliably supported with Django 2.0?
- What upgrade strategies = or methods have worked well for you in similar environments?
- Any gotch= as or performance considerations to keep in mind with large databases durin= g such upgrades?

Your recommendations and experiences will be extrem= ely valuable in helping us plan and execute this upgrade smoothly.

T= hank you in advance for your support!
--000000000000523b12063749a5c6--