Re: 7.4 Press Release -- Draft #4 - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: 7.4 Press Release -- Draft #4
Date
Msg-id 200307281356.59632.josh@agliodbs.com
Whole thread Raw
In response to Re: 7.4 Press Release -- Draft #4  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: 7.4 Press Release -- Draft #4
List pgsql-advocacy
Robert,

> Aside from spec compliance, whats the bonus for having it then? Or put a
> better way, why/when would I want to use this?

One scenario:  You have 5 PostgreSQL servers connecting to one SAN or NAS
which is your /data directory for a single database.   You use your
middleware to distribute requests among the servers; One server gets data
write requests, the other 4 get read-only requests.

However, you want to make sure that if your middleware hiccups you don't
corrupt the database files.  For this, setting 4 of the servers to "Read Only
Transactions" would be useful.

--
-Josh Berkus
 Aglio Database Solutions
 San Francisco


pgsql-advocacy by date:

Previous
From: "Nick Fankhauser"
Date:
Subject: Re: 7.4 Press Release -- starting Draft #5
Next
From: Christopher Browne
Date:
Subject: Why READ ONLY transactions?