From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Daniel Duvall" <the(dot)liberal(dot)media(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: postgresql clustering |
Date: | 2005-09-30 20:49:22 |
Message-ID: | BF62F2E2.1061B%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dan,
On 9/29/05 3:23 PM, "Daniel Duvall" <the(dot)liberal(dot)media(at)gmail(dot)com> wrote:
> What about clustered filesystems? At first blush I would think the
> overhead of something like GFS might kill performance. Could one
> potentially achieve a fail-over config using multiple nodes with GFS,
> each having there own instance of PostgreSQL (but only one running at
> any given moment)?
Interestingly - my friend Matt O'Keefe built GFS at UMN, I was one of his
first customers/sponsors of the research in 1998 when I implemented an
8-node shared disk cluster on Alpha Linux using GFS and Fibre Channel.
Again - it depends on what you're doing - if it's OLTP, you will spend too
much time in lock management for disk access and things like Oracle RAC's
CacheFusion becomes critical to reduce the number of times you have to hit
disks. For warehousing/sequential scans, this kind of clustering is
irrelevant.
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-09-30 20:54:39 | Re: effective SELECT from child tables |
Previous Message | Bill Bartlett | 2005-09-30 20:48:11 | Request for a "force interactive mode" flag (-I) for psql |