From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC 2018 |
Date: | 2017-12-15 12:01:55 |
Message-ID: | 20171215120155.GG4628@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Aleksander,
* Aleksander Alekseev (a(dot)alekseev(at)postgrespro(dot)ru) wrote:
> > New entries are certainly welcome and encouraged, just be sure to note
> > them as '2018' when you add it.
>
> I proposed a few ideas:
Thanks!
> * High availability / failover based on logical replication
> * Thrift datatype support
>
> Hope these ideas are good enough for GSoC.
The main things are to have a detailed enough description that someone
can write a project plan about what they're going to do over the summer
on that project and the project is of a reasonable size.
HA/fail-over is a very broad topic, with a lot of pieces that need to be
done such that I'm not sure it's really viable, but perhaps a precursor
project (synchronous logical replication seems like a prereq, no?) would
make more sense. Or, perhaps, a different piece of the HA question, but
solving the whole thing in a summer strikes me as unlikely to be
reasonable.
Regarding the thrift data type, that seems like a pretty good GSoC
project, though I'm not sure why you suggest having pl/pgsql functions
for accessing data from .thrift files- plpgsql can't directly access the
filesystem and the input routines for .thrift-style data would certainly
be best in C.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2017-12-15 12:57:50 | Re: GSoC 2018 |
Previous Message | Christoph Berg | 2017-12-15 11:53:31 | Re: Package version in PG_VERSION and version() |