Re: Some thoughts on table inheritance (which is uniquely awesome on PostgreSQL)

From: Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)gmail(dot)com>
Subject: Re: Some thoughts on table inheritance (which is uniquely awesome on PostgreSQL)
Date: 2012-08-24 02:17:43
Message-ID: CAM6mieKjPY=rUd74MKeKruYX0tD5vHtxmrTv+FBrLuzVDrVChw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On 24 August 2012 11:44, Chris Travers <chris(dot)travers(at)gmail(dot)com> wrote:
> One thing I have found looking through Oracle and DB2 docs is that
> their table inheritance seems to have all the same problems as ours
> and their solutions to these problems seem rather.... broken from a
> pure relational perspective.

I can second that. Additionally, some vendors tried to fix
partitioning (which uses table inheritance) issues by creating all
sort of extension like CREATE TABLE ... PARTITION BY, and ALTER TABLE
... ALTER PARTITION ... which create all sorts of issues which are not
documented at all but you get response like "yes, we know about this
bug; fix not yet available".

Many people asked for "SQL wrappers" for table partitioning but that's
not easy to do. I would be happy to have out of the box "auto-routing"
for insert/update/copy statements

--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Edson Richter 2012-08-24 02:18:14 Postgresql 9.1 on VMWare ESXi 5.0
Previous Message Craig Ringer 2012-08-24 02:12:20 Re: Can column name aliases be supported?