pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Travers <chris@travelamericas.com>
To: Spiegelberg, Greg <gspiegelberg@cranel.com>
To: pgsql-admin@postgresql.org
Subject: Re: postgresql cluster on SAN
Date: Fri, 23 Sep 2005 12:57:42 -0700
Message-ID: <43345E36.1020201@travelamericas.com> (raw)
In-Reply-To: <82E74D266CB9B44390D3CCE44A781ED96B500D@POSTOFFICE.cranel.local>
References: <82E74D266CB9B44390D3CCE44A781ED96B500D@POSTOFFICE.cranel.local>

Spiegelberg, Greg wrote:

>This is possible.  Below is a brief recipe.
>
>1. Use Veritas Storage Foundation HA with Cluster File System.
>2. Have a volume with cfs available to 2 or more systems via SAN.
>3. Install PostgreSQL and be sure PGDATA is on the cfs mount
>4. Create a Storage Checkpoint of cfs mount (read-write virtual copy)
>5. Bring up PostgreSQL on node1
>6. Mount storage checkpoint on node2
>7. Start PostgreSQL on node2
>
>Drawbacks?  Heck yes.  There are many and you should understand the
>nature of Veritas Storage Checkpoints before using.
>
Drawback #1-- only works read-only on all but one node.  And I am not 
even sure what will happen when you start writing on that one node...

>  I have tested it
>though in conjunction with dblink() and some other proprietary API's we
>use for load balancing and the potential is there to manage many large
>SELECT's.
>  
>
Ok, but what happens when you start doing inserts, updates, and deletes.

Somehow I think that PostgreSQL's dependance on shmem and semaphores 
will cause corruption in your database as soon as you start writing to 
it on both nodes.  And I don't know enough about PostgreSQL's internal 
structure to know if writing on only one node is safe.

Best Wishes,
Chris Travers
Metatron Technology Consulting



view thread (12+ messages)  latest in thread

Message-ID: <43345E36.1020201@travelamericas.com>
Permalink:  ../43345E36.1020201@travelamericas.com/
Also on:    postgresql.org/message-id/43345E36.1020201@travelamericas.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: chris@travelamericas.com, gspiegelberg@cranel.com
  Subject: Re: postgresql cluster on SAN
  In-Reply-To: <43345E36.1020201@travelamericas.com>
  References: <82E74D266CB9B44390D3CCE44A781ED96B500D@POSTOFFICE.cranel.local> <43345E36.1020201@travelamericas.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