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
On 14 May 2013 20:04, Peter Geoghegan wrote:
> On Tue, May 14, 2013 at 11:47 AM, Heikki Linnakangas
> wrote:
>> I've been thinking, we should already start collecting ideas for next year,
>> and collect them throughout the year. I know I come up with some ideas every
>> now and then, but when it'
On Tue, May 14, 2013 at 11:47 AM, Heikki Linnakangas
wrote:
> I've been thinking, we should already start collecting ideas for next year,
> and collect them throughout the year. I know I come up with some ideas every
> now and then, but when it's time for another GSoC, I can't remember any of
> th
On 14 May 2013 19:47, Heikki Linnakangas wrote:
> 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
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 ...?
I've been thinking, we shou
> 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 ...?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Se
On 05/14/2013 10:05 AM, Simon Riggs wrote:
> I'm proposing this now as a possible GSoC project:
>
> In 1-byte character encodings (i.e. not UTF-8), SUBSTR() is optimised
> to allow seeking straight to the exact slice when retrieving a large
> toasted value. This reduces I/O considerably when you ha
I'm proposing this now as a possible GSoC project:
In 1-byte character encodings (i.e. not UTF-8), SUBSTR() is optimised
to allow seeking straight to the exact slice when retrieving a large
toasted value. This reduces I/O considerably when you have large
toasted values since it is an O(1) action r