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

From Julien Rouhaud
Subject Re: Data loss when '"json_populate_recorset" with long column name
Date
Msg-id CAOBaU_YyeHOzBchVwKV_3CB4xLPm-wNATyLLKKcGMwvPzkZ84w@mail.gmail.com
Whole thread Raw
In response to Re: Data loss when '"json_populate_recorset" with long column name  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Data loss when '"json_populate_recorset" with long column name
List pgsql-hackers
On Tue, Sep 7, 2021 at 1:31 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> Yeah.  We should try to work toward removing the limits on NAMEDATALEN
> for the attribute names.  Easier said than done :)

Yes, but even if we eventually fix that my impression is that we would
still enforce a limit of 128 characters (or bytes) as this is the SQL
specification.  So trying to rely on json identifiers having the same
rules as SQL identifiers sounds like the wrong approach.



pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: stat() vs ERROR_DELETE_PENDING, round N + 1
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: [BUG] Failed Assertion in ReorderBufferChangeMemoryUpdate()