Re: Test mail for pgsql-hackers

From: BharatDB <bharatdbpg(at)gmail(dot)com>
To: pgsql-hackers Owner <pgsql-hackers-owner(at)lists(dot)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Test mail for pgsql-hackers
Date: 2025-03-11 12:33:09
Message-ID: CAAh00ETfXo7VLXy61oHL_u3vGKeer=HVjQ4GeS2UHiB=nXCbWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

>
> Hi ,

> I’ve been exploring logical replication and noticed that if the column
> datatypes don’t match between the publisher and subscriber, PostgreSQL
> doesn’t give a warning. This can cause unexpected behavior, and I thought
> it might be helpful to alert users when this happens.

> ### **What This Patch Does:**

> - Adds a warning when a column's datatype in the subscriber doesn’t match
> the publisher.

- Helps users catch issues early instead of running into silent errors
> later.

> Why I Think It’s Useful:- Avoids confusion when replication doesn’t work
> as expected. - Makes debugging easier by pointing out potential problems.
> I’d love to get feedback on whether this is a good idea and if I’ve
> approached it correctly. Since I’m still learning, any suggestions for
> improvement would be really helpful. I’ve attached the patch—please let me
> know what you think!

> Thanks, Blessy

Attachment Content-Type Size
Datatype_mismatch_logicalreplication_.patch text/x-patch 48.3 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruno Friedmann 2025-03-11 12:36:53 Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
Previous Message Laurenz Albe 2025-03-11 11:58:37 Re: Unqualified name not resolved in function called from materialized view (17.4)

Browse pgsql-hackers by date

  From Date Subject
Next Message BharatDB 2025-03-11 12:37:19 Fwd: Test mail for pgsql-hackers
Previous Message Junwang Zhao 2025-03-11 12:19:25 Re: SQL Property Graph Queries (SQL/PGQ)