pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pavel Golub <pavel@microolap.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org, Pavel Stehule <pavel.stehule@gmail.com>
Subject: Re: Slicing TOAST
Date: Wed, 15 May 2013 12:01:51 +0300
Message-ID: <1886757050.20130515120151@gf.microolap.com> (raw)
In-Reply-To: <519286BB.6080901@vmware.com>
References: <CA+U5nMJGgJNt5VXqkR=crtDqXFmuyzwEF23-fD5NuSns+6N5dA@mail.gmail.com>
	<WM!ca9f4a2b3dfec7ec66c12d42de1466aff0a8588b58f8fbe93f73821c22754474b2a2a5bcf368d351ca53f810d8b9f70e!@asav-3.01.com>
	<51928433.1040700@agliodbs.com>
	<519286BB.6080901@vmware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Hello, Heikki.

You wrote:

HL> On 14.05.2013 21:36, Josh Berkus wrote:
>>
>>> I'm proposing this now as a possible GSoC project; I don't propose to
>>> actively work on it myself.
>>
>> The deadline for submitting GSOC projects (by students) was a week ago.
>>   So is this a project suggestion for next year ...?


HL> I've been thinking, we should already start collecting ideas for next 
HL> year, and collect them throughout the year. I know I come up with some
HL> ideas every now and then, but when it's time for another GSoC, I can't
HL> remember any of them.

HL> I just created a GSoC2014 ideas pages on the wiki, for collecting these:
HL> https://wiki.postgresql.org/wiki/GSoC_2014. Let's keep the ideas coming,
HL> throughout the year.

Good idea! It reminds about feature proposed by Pavel Stehule while
ago here: http://www.postgresql.org/message-id/BANLkTini+ChGKfnyjkF1rsHSQ2kMktSDjg@mail.gmail.com

It's about streaming functionality for BYTEA type. But I think
streaming must be added to BYTEA, TEXT and VARCHAR without length
specifier too.

As Pavel stated: "A very large bytea are limited by
query size - processing long query needs too RAM". This is the holy
true, which came up suddenly in the project of one of my client.
Becuase he used bytea for images storing and text format in
PQexec, which as you know doubles-triples size of the data.

Some more details from Pavel:
<quote>
There is a few disadvantages LO against bytea, so there are requests
for "smarter" API for bytea.

Significant problem is different implementation of LO for people who
have to port application to PostgreSQL from Oracle, DB2. There are
some JDBC issues too.

For me - main disadvantage of LO in one space for all. Bytea removes
this disadvantage, but it is slower for lengths > 20 MB. It could be
really very practical have a possibility insert some large fields in
second NON SQL stream. Same situation is when large bytea is read.
</quote>

I'm not sure if the whole project is simple enough for GSOC, but I
suppose it may be splitted somehow.

PS Should we start separate thread for proposals, because I've spent
an hour since I found wiki for GSOC14 mention.


HL> - Heikki





-- 
With best wishes,
 Pavel                          mailto:pavel@gf.microolap.com



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (13+ messages)

Message-ID: <1886757050.20130515120151@gf.microolap.com>
Permalink:  ../1886757050.20130515120151@gf.microolap.com/
Also on:    postgresql.org/message-id/1886757050.20130515120151@gf.microolap.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-students@postgresql.org
  Cc: pavel@microolap.com, hlinnakangas@vmware.com, josh@agliodbs.com, pavel.stehule@gmail.com
  Subject: Re: Slicing TOAST
  In-Reply-To: <1886757050.20130515120151@gf.microolap.com>
  References: <CA+U5nMJGgJNt5VXqkR=crtDqXFmuyzwEF23-fD5NuSns+6N5dA@mail.gmail.com> <WM!ca9f4a2b3dfec7ec66c12d42de1466aff0a8588b58f8fbe93f73821c22754474b2a2a5bcf368d351ca53f810d8b9f70e!@asav-3.01.com> <51928433.1040700@agliodbs.com> <519286BB.6080901@vmware.com> <1886757050.20130515120151@gf.microolap.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox