Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Postgres on Netapp

From: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
To: Larry Rosenman <ler(at)lerctr(dot)org>, Shankar K <shan0075(at)yahoo(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [PERFORM] Postgres on Netapp
Date: 2004-01-17 16:55:13
Message-ID: 200401171155.13281.darcy@druid.net (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-performance
On January 16, 2004 11:53 am, Larry Rosenman wrote:
> --On Monday, January 12, 2004 13:45:45 -0800 Shankar K <shan0075(at)yahoo(dot)com>
> wrote:
> > We are considering to use NetApp filer for a highly
> > busy 24*7 postgres database and the reason we chose
> I run a (not very busy) PG cluster on a NetAPP.

I run a very busy PG installation on one.

> It seems to do just fine.

Ditto.

> The issue is the speed of the network connection.  In my case it's only
> FastEthernet (100BaseTX).  If it's very busy, you may need to look
> at GigE.

With the price of GigE adapters I wouldn't consider anything else.

I have a huge database that takes about an hour to copy.  The netApp snapshot 
feature is very nice because I can get a "moment in time" image of the 
database.  Even though I can't run from the snapshot because it is read only 
(*) and PG needs to write to files just to open the database, I can copy it 
and get a runnable version of the DB.  If I copy directly from the original I 
can get many changes while copying and wind up with a copy that will not run.

(*): It would be nice if PG had a flag that allowed a database to be opened in 
read only mode without touching anything in the directory.

-- 
D'Arcy J.M. Cain <darcy(at){druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2004-01-17 17:32:33
Subject: Re: Idle postmaster taking up a lot of CPU
Previous:From: John SiracusaDate: 2004-01-17 15:34:22
Subject: Idle postmaster taking up a lot of CPU

pgsql-admin by date

Next:From: kdykeDate: 2004-01-18 00:52:28
Subject: error on build from source
Previous:From: Warren LittleDate: 2004-01-17 00:57:24
Subject: setting statement_timeout on live postmaster

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group