pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: PFC <lists@boutiquenumerique.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Sat, 19 Mar 2005 23:47:53 -0500
Message-ID: <4507.1111294073@sss.pgh.pa.us> (raw)
In-Reply-To: <20050320042917.GA25831@dcc.uchile.cl>
References: <200503191202.38089.josh@agliodbs.com>
	<op.snwojdwith1vuj@localhost>
	<20050319225624.GA8467@dcc.uchile.cl>
	<3404.1111277153@sss.pgh.pa.us>
	<20050320042917.GA25831@dcc.uchile.cl>

Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Hmm.  You are right, but without that we won't be able to enforce
> uniqueness on the partitioned table (we could only enforce it on each
> partition, which would mean we can't partition on anything else than
> primary keys if the tables have one).  IMHO this is something to
> consider.

Well, partitioning on the primary key would be Good Enough for 95% or
99% of the real problems out there.  I'm not excited about adding a
large chunk of complexity to cover another few percent.

			regards, tom lane



view thread (45+ messages)  latest in thread

Message-ID: <4507.1111294073@sss.pgh.pa.us>
Permalink:  ../4507.1111294073@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4507.1111294073@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, alvherre@dcc.uchile.cl, lists@boutiquenumerique.com, josh@agliodbs.com
  Subject: Re: What needs to be done for real Partitioning?
  In-Reply-To: <4507.1111294073@sss.pgh.pa.us>

* 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