| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JsonPath version bits |
| Date: | 2023-03-30 12:16:39 |
| Message-ID: | CAN-LCVOGvA=4gTCW9FEj5k5rXNotPVjovd4_eEa8yhV1o7pr=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers!
Could the 1 byte from the JsonPath header be used to store version?
Or how many bits from the header could be used for the version value?
On Mon, Mar 27, 2023 at 12:54 PM Nikita Malakhov <hukutoc(at)gmail(dot)com> wrote:
> Hi hackers!
>
> I've got a question on the JsonPath header - currently the header size
> is 4 bytes, where there are version and mode bits. Is there somewhere
> a defined size of the version part? There are some extensions working
> with JsonPath, and we have some too, thus it is important how many
> bits is it possible to use to store a version value?
>
>
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-03-30 12:58:20 | Re: postgres_fdw, dblink, and CREATE SUBSCRIPTION security |
| Previous Message | Merlin Moncure | 2023-03-30 12:06:48 | Re: Request for comment on setting binary format output per session |