Re: Data loss when '"json_populate_recorset" with long column name

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Денис Романенко <deromanenko(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Data loss when '"json_populate_recorset" with long column name
Date: 2021-09-07 05:31:03
Message-ID: YTb5F5/jwZNOwf37@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-09-07 05:35:54 Re: Column Filtering in Logical Replication
Previous Message Michael Paquier 2021-09-07 05:28:16 Re: when the startup process doesn't (logging startup delays)