Re: Optimizing pglz compressor

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Optimizing pglz compressor
Date: 2013-03-01 15:42:30
Message-ID: 5130CC66.6020802@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01.03.2013 17:37, Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>
>> In summary, this seems like a pretty clear win for short values, and
>> a wash for long values. Not surprising, as this greatly lowers the
>> startup cost of pglz_compress(). We're past feature freeze, but how
>> would people feel about committing this?
>
> Surely we're not past feature freeze. If we were, we'd have to reject
> all remaining patches from the commitfest, which is not what we want to
> do at this stage, is it?

Right, no, that's not what I meant by feature freeze. I don't know what
the correct term here would be, but what I meant is that we're not
considering new features for 9.3 anymore, except those that are in the
commitfest.

> My take on this is that if this patch is necessary to get Amit's patch
> to a commitable state, it's fair game.

I don't think it's necessary for that, but let's see..

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-03-01 15:44:49 Re: Optimizing pglz compressor
Previous Message Alvaro Herrera 2013-03-01 15:37:43 Re: Optimizing pglz compressor