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

help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndQuadrant.com>
To: Vincenzo Romano <vincenzo.romano@notorand.it>
Cc: pgsql-hackers@postgresql.org
Subject: Re: On Scalability
Date: Thu, 07 Oct 2010 22:42:59 +0100
Message-ID: <1286487779.2304.372.camel@ebony> (raw)
In-Reply-To: <AANLkTi==OD9afGEDOm7OY3KYydLXcMj=kO7M5+QFbaM0@mail.gmail.com>
References: <AANLkTi=6=WRpND-MXv92D-+iC9AnYDwLsbbXMXj4uNky@mail.gmail.com>
	<1280423526.8613.36.camel@jd-desktop.unknown.charter.com>
	<AANLkTikV96eAFxEuqk4k6jadtDomLhnJrwqtEh3mNKs6@mail.gmail.com>
	<1280425184.8613.41.camel@jd-desktop.unknown.charter.com>
	<AANLkTim7HQQz=qGfW=xDhx-8HNppYxXF48NjnU2-XiNt@mail.gmail.com>
	<1280427410.8613.44.camel@jd-desktop.unknown.charter.com>
	<AANLkTimSGghp4TseAV-zgNYakkyH3J_jW2k8peL7EOTv@mail.gmail.com>
	<4CAD769D.9090301@enterprisedb.com>
	<1286437290.2304.192.camel@ebony>
	<4CAD7BED.4050009@enterprisedb.com>
	<AANLkTi==OD9afGEDOm7OY3KYydLXcMj=kO7M5+QFbaM0@mail.gmail.com>

On Thu, 2010-10-07 at 14:10 +0200, Vincenzo Romano wrote:

> Making these things sub-linear (whether not O(log n) or even O(1) ),
> provided that there's  way to, would make this RDBMS more appealing
> to enterprises.
> I mean also partial indexes (as an alternative to table partitioning).
> Being able to effectively cope with "a dozen child tables or so" it's more
> like an amateur feature.
> If you really need partitioning (or just hierarchical stuff) I think you'll need
> for quite more than a dozen items.
> If you partition by just weeks, you'll need 50+ a year.
> 
> Is there any precise direction to where look into the code for it?
> 
> Is there a way to put this into a wish list?

It's already on the wish list ("TODO") and has been for many years.

We've mostly lacked somebody with the experience and time/funding to
complete that implementation work. I figure I'll be doing it for 9.2
now; it may be difficult to do this for next release.

Theoretically, this can be O(n.log n) for range partitioning and O(1)
for exact value partitioning, though the latter isn't a frequent use
case.

Your conclusion that the current partitioning only works with a dozen or
so items doesn't match the experience of current users however.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Development, 24x7 Support, Training and Services




view thread (45+ messages)  latest in thread

Message-ID: <1286487779.2304.372.camel@ebony>
Permalink:  ../1286487779.2304.372.camel@ebony/
Also on:    postgresql.org/message-id/1286487779.2304.372.camel@ebony

 · 

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-performance@postgresql.org
  Cc: simon@2ndQuadrant.com, vincenzo.romano@notorand.it, pgsql-hackers@postgresql.org
  Subject: Re: On Scalability
  In-Reply-To: <1286487779.2304.372.camel@ebony>

* 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