Re: Proposal: Conflict log history table for Logical Replication

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, saurabh singh <saurabh(dot)singh214(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Proposal: Conflict log history table for Logical Replication
Date: 2026-09-01 10:32:46
Message-ID: CAJpy0uD9zYY0Q+RkbFAetxhBuXfuhu5jt6=PFNf0f6Bi7FPTDw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I found a case where Numeric goes up to 50K and is not omitted. As per
doc([1]), numeric can go up to 131072 digits , which means it can
easily go beyond 16k limit. See the test attached. I think
JSONTYPE_NUMERIC in datum_to_json_internal() also needs the fix.
Attached the patch for potential fix. It applies on top of
0001-reentrant-json-fix.patch shared in previous email.

[1]: https://www.postgresql.org/docs/19/datatype-numeric.html

thanks
Shveta

Attachment Content-Type Size
json_numeric.txt text/plain 500 bytes
0001-json-numeric-fix.patch application/octet-stream 2.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Geier 2026-09-01 11:05:23 Re: Reduce build times of pg_trgm GIN indexes
Previous Message Alexandre Felipe 2026-09-01 10:27:22 Re: SLOPE - Planner optimizations on monotonic expressions.