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

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 06:00:28
Message-ID: CAOBaU_YyeHOzBchVwKV_3CB4xLPm-wNATyLLKKcGMwvPzkZ84w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 7, 2021 at 1:31 PM Michael Paquier <michael(at)paquier(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2021-09-07 06:03:38 Re: [BUG] Failed Assertion in ReorderBufferChangeMemoryUpdate()
Previous Message Alexander Lakhin 2021-09-07 06:00:01 Re: stat() vs ERROR_DELETE_PENDING, round N + 1