Re: SQL JSON path enhanced numeric literals

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Nikita Malakhov <hukutoc(at)gmail(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL JSON path enhanced numeric literals
Date: 2023-04-03 08:42:02
Message-ID: 02f43fb3-9a07-6c9c-9a4c-97a6b25417d5@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 31.03.23 16:57, Nikita Malakhov wrote:
> Sorry to bother, but there is a question on JsonPath - how many bits in
> the JsonPath
> header could be used for the version? The JsonPath header is 4 bytes,
> and currently
> the Version part is defined as
> #define JSONPATH_VERSION (0x01)

I don't know the answer to that. I don't think this patch touched on
that question at all.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Quan Zongliang 2023-04-03 10:23:41 Why enable_hashjoin Completely disables HashJoin
Previous Message Daniel Gustafsson 2023-04-03 08:39:41 Re: Making background psql nicer to use in tap tests