| From: | Jean-Max Reymond <jmreymond(at)gmail(dot)com> |
|---|---|
| To: | Steve Wampler <swampler(at)noao(dot)edu> |
| Cc: | Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL clustering VS MySQL clustering |
| Date: | 2005-01-20 19:35:44 |
| Message-ID: | 4b09a0c05012011355033781b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 20 Jan 2005 12:13:17 -0700, Steve Wampler <swampler(at)noao(dot)edu> wrote:
> Mitch Pirtle wrote:
> But that's not enough, because you're going to be running separate
> postgresql backends on the different hosts, and there are
> definitely consistency issues with trying to do that. So far as
> I know (right, experts?) postgresql isn't designed with providing
> distributed consistency in mind (isn't shared memory used for
> consistency, which restricts all the backends to a single host?).
yes, you're right: you'll need a Distributed Lock Manager and an
application to manage it , Postgres ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-01-20 20:00:17 | Re: PostgreSQL clustering VS MySQL clustering |
| Previous Message | Merlin Moncure | 2005-01-20 19:29:34 | Re: [SQL] OFFSET impact on Performance??? |