pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schaber <schabios@logi-track.com>
To: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date: Thu, 16 Sep 2004 15:38:21 +0200
Message-ID: <20040916153821.1d5716ca@kingfisher.intern.logi-track.com> (raw)
In-Reply-To: <20040916041703.GA23118@gp.word-to-the-wise.com>
References: <m3acvulx5f.fsf@wolfe.cbbrowne.com>
	<NOEFLCFHBPDAFHEIPGBOCEFPCEAA.simon@2ndquadrant.com>
	<20040914223333.GL56059@decibel.org>
	<20040915051003.GA32043@gp.word-to-the-wise.com>
	<20040915111644.7cac2433@kingfisher.intern.logi-track.com>
	<20040916041703.GA23118@gp.word-to-the-wise.com>

Hi, Steve,

On Wed, 15 Sep 2004 21:17:03 -0700
Steve Atkins <steve@blighty.com> wrote:

> On Wed, Sep 15, 2004 at 11:16:44AM +0200, Markus Schaber wrote:
> > But you have to add table constraints restricting the time after adding
> > the partition?
> 
> Uhm... unless I'm confused that's not a meaningful thing in this context.
> There's no rule that's putting insertions into an inherited table - the
> decision of which inherited table to insert into is made at application
> level.

I thought of the query optimizer. I thought it could use the table
constraints to drop tables when creating the union. But now I think that
an index gives enough win, because the tree-based indices are rather
quick at returning zero rows when the queried value is out of the
indexed range.

Greetings,
Markus


-- 
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com



view thread (52+ messages)  latest in thread

Message-ID: <20040916153821.1d5716ca@kingfisher.intern.logi-track.com>
Permalink:  ../20040916153821.1d5716ca@kingfisher.intern.logi-track.com/
Also on:    postgresql.org/message-id/20040916153821.1d5716ca@kingfisher.intern.logi-track.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: schabios@logi-track.com
  Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
  In-Reply-To: <20040916153821.1d5716ca@kingfisher.intern.logi-track.com>
  References: <m3acvulx5f.fsf@wolfe.cbbrowne.com> <NOEFLCFHBPDAFHEIPGBOCEFPCEAA.simon@2ndquadrant.com> <20040914223333.GL56059@decibel.org> <20040915051003.GA32043@gp.word-to-the-wise.com> <20040915111644.7cac2433@kingfisher.intern.logi-track.com> <20040916041703.GA23118@gp.word-to-the-wise.com> <20040916153821.1d5716ca@kingfisher.intern.logi-track.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