> I'm applying for GSoC 2014 with Postgresql and would appreciate your comments > on my proposal > (attached). I'm looking for technical corrections/comments and your opinions > on the project's > viability. In particular, if the community has doubts about its usefulness, I > would start working on > an extra proposal from https://wiki.postgresql.org/wiki/GSoC_2014, perhaps on > the RETURNING clause as > a student named Karlik did last year.
I am sure that Simon had his reasons when he proposed http://www.postgresql.org/message-id/CA+U5nMJGgJNt5VXqkR=crtdqxfmuyzwef23-fd5nusns+6n...@mail.gmail.com but I cannot help asking some questions: 1) Why limit the feature to UTF8 strings? Shouldn't the technique work for all multibyte server encodings? 2) There is probably something that makes this necessary, but why should the decision how toast is sliced be attached to the data type? My (probably naive) idea would be to add a new TOAST strategy (e.g. SLICED) to PLAIN, MAIN, EXTERNAL and EXTENDED. The feature only makes sense for string data types, right? Yours, Laurenz Albe -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
