From: Joshua D. Drake <jd@commandprompt.com>
To: Vincenzo Romano <vincenzo.romano@notorand.it>
Cc: pgsql-hackers@postgresql.org
Subject: Re: On Scalability
Date: Thu, 29 Jul 2010 10:39:44 -0700
Message-ID: <1280425184.8613.41.camel@jd-desktop.unknown.charter.com> (raw)
In-Reply-To: <AANLkTikV96eAFxEuqk4k6jadtDomLhnJrwqtEh3mNKs6@mail.gmail.com>
References: <AANLkTi=6=WRpND-MXv92D-+iC9AnYDwLsbbXMXj4uNky@mail.gmail.com>
<1280423526.8613.36.camel@jd-desktop.unknown.charter.com>
<AANLkTikV96eAFxEuqk4k6jadtDomLhnJrwqtEh3mNKs6@mail.gmail.com>
On Thu, 2010-07-29 at 19:34 +0200, Vincenzo Romano wrote:
> I expect that a more complex schema will imply higher workloads
> on the query planner. What I don't know is how the increase in the
> workload will happen: linearly, sublinearly, polinomially or what?
>
> Significant testing would require a prototype implementation with
> an almost complete feed of data from the current solution.
> But I'm at the feasibility study stage and have not enough resources
> for that.
>
> Thanks anyway for the insights, Joshua.
> Does the 60-100 tables limit applies to a single level
> of inheritance? Or is it more general?
I do not currently have experience (except that it is possible) with
multi-level inheritance and postgresql.
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
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: jd@commandprompt.com, vincenzo.romano@notorand.it, pgsql-hackers@postgresql.org
Subject: Re: On Scalability
In-Reply-To: <1280425184.8613.41.camel@jd-desktop.unknown.charter.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