| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Adrian 'Dagurashibanipal' von Bidder" <avbidder(at)fortytwo(dot)ch> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is MySQL more chosen over PostgreSQL? |
| Date: | 2002-07-30 08:45:43 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOOEGLCDAA.chriskl@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > We inherited inheritance from Berkeley. I doubt we would have added it
> > ourselves. It causes too much complexity in other parts of the system.
>
> How about dropping it, then?
>
> Just start to emit
>
> WARNING: inheritance will be dropped with postgres 8.0
> WARNING: please refer to http://.../ for an explanation why.
>
> right now on every CREATE TABLE that uses it.
Why? It doesn't hurt you personally! Plus, it would annoy a _boatload_ of
existing inheritance users.
A more interesting question I think is how to allow our indexes to span
multiple relations, _without_ causing any performance degradation for non
inheritance users...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian 'Dagurashibanipal' von Bidder | 2002-07-30 09:51:45 | Re: Why is MySQL more chosen over PostgreSQL? |
| Previous Message | Adrian 'Dagurashibanipal' von Bidder | 2002-07-30 08:19:39 | Re: Why is MySQL more chosen over PostgreSQL? |