Re: GSoC 2018: thrift encoding format

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>
Cc: Charles Cui <charles(dot)cui1984(at)gmail(dot)com>, 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-04 10:31:50
Message-ID: CAB=Je-GHfkG9nkrJUUm7oPK9XFA2-EVXogcwmweENGpkvoVDJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>I mean Charles is free to choose the interface for the extension he
believes is right

I'm just trying to figure out what are the use cases for using that Thrift
extension.

For instance, it would be interesting if Thrift was an alternative way to
transfer data between client and the database. I guess it could simplify
building efficient clients.

Vladimir

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2018-05-04 10:59:35 pg_rewind and postgresql.conf
Previous Message Teodor Sigaev 2018-05-04 09:39:15 Re: nbtsort.c performs unneeded (though harmless) truncation