MIME-Version: 1.0
From: Sasmit Utkarsh <utkarshsasmit@gmail.com>
Date: Tue, 3 Dec 2024 23:13:46 +0530
Message-ID: <CAM-5MT2gc+=tm5ErdoEyHDef3NzNL2UbAkrykdca9=1VJZi4fg@mail.gmail.com>
Subject: Best Practices for Managing Schema Changes Dynamically with libpq
To: pgsql-general <pgsql-general@postgresql.org>, pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a86db10628613544"
Archived-At: <https://www.postgresql.org/message-id/CAM-5MT2gc%2B%3Dtm5ErdoEyHDef3NzNL2UbAkrykdca9%3D1VJZi4fg%40mail.gmail.com>
Precedence: bulk

--000000000000a86db10628613544
Content-Type: text/plain; charset="UTF-8"

Dear PostgreSQL Community Team,

I am working on a project that uses libpq along with C language to interact
with PostgreSQL, and we face challenges with managing schema changes
dynamically in production while avoiding downtime. Specifically, we need
guidance on handling table structure changes/additions without tightly
coupling these changes to application updates.

*Current Approach:*
Schema changes are deployed first, followed by application updates to align
with the new structure.

*Challenges:*
Ensuring application stability during the transitional phase when the
schema and code are not fully in sync.
Handling table structure changes (e.g., adding new columns) dynamically
without requiring immediate code changes.

*Questions:*
Are there recommended best practices for managing such schema changes with
libpq?
How can we efficiently handle table additions/updates while keeping the
application and database in sync dynamically?

I would appreciate any guidance, patterns, or examples that can help us
implement a robust solution.

Thank you for your time and support!

Regards,
Sasmit Utkarsh
+91-7674022625

--000000000000a86db10628613544
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear PostgreSQL Community Team,<br><br>I am working o=
n a project that uses libpq along with C language to interact with PostgreS=
QL, and we face challenges with managing schema changes dynamically in prod=
uction while avoiding downtime. Specifically, we need guidance on handling =
table structure changes/additions without tightly coupling these changes to=
 application updates.<br><br><b>Current Approach:</b><br>Schema changes are=
 deployed first, followed by application updates to align with the new stru=
cture.<br><br><b>Challenges:</b><br>Ensuring application stability during t=
he transitional phase when the schema and code are not fully in sync.<br>Ha=
ndling table structure changes (e.g., adding new columns) dynamically witho=
ut requiring immediate code changes.<br><br><b>Questions:</b><br>Are there =
recommended best practices for managing such schema changes with libpq?<br>=
How can we efficiently handle table additions/updates while keeping the app=
lication and database in sync dynamically?<br><br>I would appreciate any gu=
idance, patterns, or examples that can help us implement a robust solution.=
<br><br>Thank you for your time and support!</div><div><br></div><div><div =
dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><d=
iv dir=3D"ltr"><div>Regards,<br></div><div>Sasmit Utkarsh</div><div>+91-767=
4022625</div></div></div></div></div>

--000000000000a86db10628613544--