Re: Abbreviated keys for text cost model fix - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Abbreviated keys for text cost model fix
Date
Msg-id CA+Tgmob3N+8bsmnmVqeU8z5tkvGExTEhDsvt9a=6uqb1wKM+GA@mail.gmail.com
Whole thread Raw
In response to Re: Abbreviated keys for text cost model fix  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Abbreviated keys for text cost model fix
List pgsql-hackers
On Mon, Feb 23, 2015 at 7:44 PM, Peter Geoghegan <pg@heroku.com> wrote:
> On Mon, Feb 23, 2015 at 4:41 PM, Tomas Vondra
> <tomas.vondra@2ndquadrant.com> wrote:
>> Are you going to add this into the CF? Would be nice to get this into
>> 9.5. Strictly speaking it should go to 2015-06 I guess, but I'd consider
>> it part of one of the existing sortsupport patches.
>
> It's a bugfix, IMV. I guess I should add it to the current CF, but I
> think I might be forbidden from doing so as a non-CF-manager...

Committed.  For future reference, I'd prefer to have things like this
added to the next CF rather than no CF at all.

I'm not sure if you've got all the details right here, but the concept
makes sense to me: if we're going to give up, we should do it early.
Doing it later throws away more work and is therefore riskier.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Cube extension kNN support
Next
From: Fujii Masao
Date:
Subject: Re: The return value of allocate_recordbuf()