| From: | Charles Cui <charles(dot)cui1984(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Subject: | Re: GSoC 2018: thrift encoding format |
| Date: | 2018-05-03 03:51:54 |
| Message-ID: | CA+SXE9vpLds-yARyJ4h3AdrVttSVNyiYtq=oMowB8rZoV2E1xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for your confirm Aleksander!
Also I am thinking of how to deal with complex
data structure like map, list, or set. I guess one possible
solution is to get raw data bytes for these data structure?
Otherwise it could be hard to wrap into a Datum.
2018-05-02 8:38 GMT-07:00 Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>:
> Hello Charles,
>
> > Can I assume the data in thrift is always send inside a struct?
>
> Sure!
>
> > I think this question also valid for protobuf?
>
> Right, pg_protobuf assumes that data is always a message which is an
> equivalent of Thrift's struct.
>
> --
> Best regards,
> Aleksander Alekseev
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-03 04:04:17 | Re: Optimize Arm64 crc32c implementation in Postgresql |
| Previous Message | Tom Lane | 2018-05-03 03:25:43 | Re: Optimize Arm64 crc32c implementation in Postgresql |