From: Joshua D. Drake <jd@commandprompt.com>
To: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: darcy@wavefire.com
Cc: jd@www.commandprompt.com
Cc: sfrost@snowman.net
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Thu, 20 Jan 2005 19:16:15 -0800
Message-ID: <41F073FF.1080606@commandprompt.com> (raw)
In-Reply-To: <20050121.104007.74755729.t-ishii@sra.co.jp>
References: <20050120144416.GO10437@ns.snowman.net>
<41EFC514.9090806@commandprompt.com>
<200501200929.37228.darcy@wavefire.com>
<20050121.104007.74755729.t-ishii@sra.co.jp>
>1) pgpool does the load balance and sends query to Slony-I's slave and
> master if the query is SELECT.
>
>2) pgpool sends query only to the master if the query is other than
> SELECT.
>
>Remaining problem is that Slony-I is not a sync replication
>solution. Thus you need to prepare that the load balanced query
>results might differ among servers.
>
>If there's enough demand, I would do such that enhancements to pgpool.
>
>
Well I know that Replicator could also use this functionality.
Sincerely,
Joshua D. Drake
>--
>Tatsuo Ishii
>
>
>
>>>>>>>Is there any other solution than a Cluster for our problem ?
>>>>>>>
>>>>>>>
>>>>>>Bigger server, more CPUs/disks in one box. Try to partition up your
>>>>>>data some way such that it can be spread across multiple machines, then
>>>>>>if you need to combine the data have it be replicated using slony to a
>>>>>>big box that has a view which joins all the tables and do your big
>>>>>>queries against that.
>>>>>>
>>>>>>
>>>>>But I'll arrive to limitation of a box size quickly I thing a 4
>>>>>processors with 64 Gb of RAM ... and after ?
>>>>>
>>>>>
>>>Opteron.
>>>
>>>
>>IBM Z-series, or other big iron.
>>
>>
>>
>>>>Go to non-x86 hardware after if you're going to continue to increase the
>>>>size of the server. Personally I think your better bet might be to
>>>>figure out a way to partition up your data (isn't that what google
>>>>does anyway?).
>>>>
>>>> Stephen
>>>>
>>>>
>>--
>>Darcy Buskermolen
>>Wavefire Technologies Corp.
>>ph: 250.717.0200
>>fx: 250.763.1759
>>http://www.wavefire.com
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>>
>>
>>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Attachments:jd.vcf (text/x-vcard, 283B) download
begin:vcard
fn:Joshua Drake
n:Drake;Joshua
org:Command Prompt, Inc.
adr:;;PO Box 215 ;Cascade Locks;OR;97014;US
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
x-mozilla-html:FALSE
url:http://www.commandprompt.com
version:2.1
end:vcard
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, t-ishii@sra.co.jp, darcy@wavefire.com, jd@www.commandprompt.com, sfrost@snowman.net, herve@elma.fr
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <41F073FF.1080606@commandprompt.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