Re: Data loss when '"json_populate_recorset" with long column name - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Data loss when '"json_populate_recorset" with long column name
Date
Msg-id YTb5F5/jwZNOwf37@paquier.xyz
Whole thread Raw
In response to Re: Data loss when '"json_populate_recorset" with long column name  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: Data loss when '"json_populate_recorset" with long column name
List pgsql-hackers
On Tue, Sep 07, 2021 at 01:11:49PM +0800, Julien Rouhaud wrote:
> Yes, that's because json identifiers have different rules from
> relation identifiers.  Your only option here is to use the real /
> truncated identifier.  Also I don't think it would be a good thing to
> add a way to truncate identifiers in json objects using the
> NAMEDATALEN limit, as this could easily lead to invalid json object
> that should be valid.

Yeah.  We should try to work toward removing the limits on NAMEDATALEN
for the attribute names.  Easier said than done :)
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: when the startup process doesn't (logging startup delays)
Next
From: Amit Kapila
Date:
Subject: Re: Column Filtering in Logical Replication