Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Constant WAL replay
- From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- To: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
- Cc: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org, eg(at)cybertec(dot)at
- Subject: Re: Constant WAL replay
- Date: Sun, 24 Apr 2005 21:18:13 -0400 (EDT)
- Message-id: <200504250118(dot)j3P1IDq14997(at)candle(dot)pha(dot)pa(dot)us>
Joshua D. Drake wrote: > >> > >>Very close. We don't use the WAL (yet, slated for probably 8.1) but we > >>do use a transaction log shipping method. So the implementation is > >>almost the same. > > > > > > Can you run queries on the slave? If so, how do you handle xid collisions? > > You can run any query that does not modify data on a replicated table. > You can run any non data modifying query on any of the tables. So, do you modify the slave to prevent it from grabbing an xid? -- Bruce Momjian | http://candle.pha.pa.us pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
- References:
- Re: Constant WAL replay
- From: Joshua D. Drake
- Re: Constant WAL replay
- Prev by Date: Re: Constant WAL replay
- Next by Date: Re: idea for concurrent seqscans
- Previous by thread: Re: Constant WAL replay
- Next by thread: Re: Constant WAL replay
- Indexes: