From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Partitioning Vs. Split Databases - performance? |
Date: | 2006-12-21 23:15:55 |
Message-ID: | 1166742955.5594.42.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2006-12-21 at 16:54 -0600, Ron Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/21/06 16:41, Joshua D. Drake wrote:
> >>>> 3) Put each customer in their own schema/namespace which resides within
> >>>> its own table space.
> >>>>
> >>>> Then you can move customers wherever you need in terms of IO.
> >> How is that functionally different than using a separate database? What's the
> >> advantage here? I don't *need* to restrict myself to one database, and doing
> >> this does require that I revisit 100% of the SQL queries to make sure that
> >> I'm referencing the right schema.
> >>
> >> This solution seems to have the same problems as using dynamic tablenames.
> >
> > Not really. You should read up on schemas and how they work. Plus the
> > addition of schemas and table spaces means you can infinite scaling
> > within the confines of your hardware itself.
>
> "infinite scaling within the confines of your hardware"!
>
> How is that accomplished?
Well with a tablespace, you can place the entire schema, easily on its
own array. Say a nice little HP-MSA30. If that array gets tired you can
add another array, and move a couple of schemas off to another array.
Also if you spec the hardware correctly, you can get up to a total of 16
cores without any significant cost... just add cpus as needed.
PostgreSQL 8.1 does extremely well up to 8 cpus (8 cores). 8.2 is said
to perform better on > 8 cores, but I have not tested it.
Sincerely,
Joshua D. Drake
>
> - --
> Ron Johnson, Jr.
> Jefferson LA USA
>
> Is "common sense" really valid?
> For example, it is "common sense" to white-power racists that
> whites are superior to blacks, and that those with brown skins
> are mud people.
> However, that "common sense" is obviously wrong.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFFixCWS9HxQb37XmcRAnw/AJ4obPHIHvJcRKq1xzILN7YtKfQscACg1uaq
> c6FRxkXjP/Pneyy1lxA+Dl8=
> =iFX6
> -----END PGP SIGNATURE-----
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Smith | 2006-12-21 23:22:11 | Re: Partitioning Vs. Split Databases - performance? |
Previous Message | Ron Johnson | 2006-12-21 22:54:14 | Re: Partitioning Vs. Split Databases - performance? |