Inheritance a burden? - Mailing list pgsql-hackers

From reina@nsi.edu (Tony Reina)
Subject Inheritance a burden?
Date
Msg-id f40d3195.0207191333.5cbb11c3@posting.google.com
Whole thread Raw
In response to Re: Planner very slow on same query to slightly  (Tony Reina <reina@nsi.edu>)
Responses Re: Inheritance a burden?  (Curt Sampson <cjs@cynic.net>)
List pgsql-hackers
As a followup to my slow query plans:

I've experimented with removing the inheritance schema to see how it
affects my database calls. Originally, because several fields of the
primary key (subject, arm, rep, direction, success) were common to
every table, I made those fields a separate table and had subsequent
tables inherit the fields. Just out of curiosity, I built a new
database with the same data but didn't use the inheritance (i.e. each
table had its own copy of those common fields). It looks like about a
20% increase in execution speed when I run my programs side by side.
I'm not sure if that kind of performance hit should be expected.
Anyone have an idea about this?

-Tony


reina@nsi.edu (Tony Reina) wrote in message news:<5.1.1.6.0.20020718095319.009ecec0@schubert.nsi.edu>...
> If I understand correctly, I tried specifying the target and even casting 
> all of the smallint's, but it still is a slow estimate. Perhaps, this is 
> just due to a large amount of data, but my gut is telling me that I have 
> something wrong here.
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: preserving statistics settings
Next
From: Alessandro Baretta
Date:
Subject: Re: Arrays and FFTW