pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Double sorting split patch
Date: Thu, 06 Oct 2011 13:19:11 +0300
Message-ID: <4E8D809F.7070304@enterprisedb.com> (raw)
In-Reply-To: <CAPpHfdtJL16zZ2uwD5LD8TnkchV-TFaLbYJeGk0ZkhcFb=KeDA@mail.gmail.com>
References: <CAPpHfdtkUfgdMwTsoNUiaKUM3HBQre1iZFiHjR2umqgTf5D_dQ@mail.gmail.com>
	<CAPpHfdsYROQbYw1kME0aro=ygLTGd8pKgYFh6GnVPO7VJTW2ew@mail.gmail.com>
	<4E74D21C.2070503@enterprisedb.com>
	<CAPpHfdsfXiQib=Jd2C4obuPQpoQ-CDPskbL-VaOaZd4uAoCOBw@mail.gmail.com>
	<CAPpHfds1YZSg6tdUrX+bFS3q=NFN+sSVx_awvbb0hKupUrmQ-g@mail.gmail.com>
	<4E7B1A7C.80103@enterprisedb.com>
	<CAPpHfdtf_sKufPJZ0XrOba8zcsWApBWUaqAPRv39niSEQYdrdA@mail.gmail.com>
	<CAPpHfdt6MO0Q9JgVXvYuf1Oe_ge_CqjCQ+ynAvYM-zEfVcEQiw@mail.gmail.com>
	<4E8AC009.5040806@enterprisedb.com>
	<CAPpHfds333E_V28nRkDY2CBSDC+TDHykZ1HBdPpYkGAjb9w6dg@mail.gmail.com>
	<4E8AD603.80506@enterprisedb.com>
	<CAPpHfds61VsxWhr4wRMZ=J4Ozp3seoS-S9bYv5Cd9Uc_UTDz+Q@mail.gmail.com>
	<4E8C091C.6020908@enterprisedb.com>
	<CAPpHfdtShbuHCooS+mPndHKubXbFVu1=XUDMibqKot+j8q3gxw@mail.gmail.com>
	<CAPpHfdvt-8vkD3p5wUCH0A3fCWtmgKxzG6bp23K4aBvOrS5Vxw@mail.gmail.com>
	<4E8D5393.2000900@enterprisedb.com>
	<CAPpHfdtJL16zZ2uwD5LD8TnkchV-TFaLbYJeGk0ZkhcFb=KeDA@mail.gmail.com>

On 06.10.2011 11:22, Alexander Korotkov wrote:
> Thanks. I'm going to continue work on application of this split method in
> following areas:
> 1) range types
> 2) seg contrib module
> 3) cube contrib module (there situation is not so easy, probably some
> heuristic of split method selection would be required)
> Do you think that separation of some common parts of algorithm implemetation
> is resonable in order to avoid code duplication? For example, different
> application of algorithm could share function of splits enumeration along
> axis which takes pointer to consider_split as an argument.

Dunno. I'd suggest that you just copy-paste the code for now, and we'll 
see how much duplication there is in the end.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (24+ messages)

Message-ID: <4E8D809F.7070304@enterprisedb.com>
Permalink:  ../4E8D809F.7070304@enterprisedb.com/
Also on:    postgresql.org/message-id/4E8D809F.7070304@enterprisedb.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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: heikki.linnakangas@enterprisedb.com, aekorotkov@gmail.com
  Subject: Re: Double sorting split patch
  In-Reply-To: <4E8D809F.7070304@enterprisedb.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