Re: dbmirror

From: "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com>
To: "Fred Fung" <fred(dot)fung(at)versaterm(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: dbmirror
Date: 2004-05-13 00:53:05
Message-ID: 71E37EF6B7DCC1499CEA0316A2568328DC9C26@loki.wc.globexplorer.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fred --

Yes, the slave database(s) can be safely used in a R/O mode, given the issue you raise of not necessarily having an up-to-date copy of the data in the master. We haven't ever run enough queries against a slave to reveal any lurking contention issues, if indeed there are any, relating to the inserts/updates being done by the dbmirror perl code (such a momentary locks), so this may need some testing under stress.

HTH,

Greg Williamson
DBA
GlobeXplorer LLC

-----Original Message-----
From: Fred Fung [mailto:fred(dot)fung(at)versaterm(dot)com]
Sent: Wednesday, May 12, 2004 8:27 AM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] dbmirror

Hi,

Does anybody know if the slave database(s) in the dbmirror replication model can be queried (via SQL SELECT statement) by a client program as if it is quering the master database (I understand that the slave database may not be a 100% mirror of the master at any given moment but that is good enough) ? We are exploring the possibility of a multi-server architecture where the master postgres database would handle all the data update maintenance workload whereas the slave(s) would handle all the query workload.

Any suggestions would be much appreciated.


TIA.


Fred


Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeffrey W. Baker 2004-05-13 01:18:40 pg_xlog becomes extremely large during CREATE INDEX
Previous Message Tom Lane 2004-05-12 22:56:11 Re: PGSTATBUFF: Warning - receive buffer full