Re: [HACKERS] Hot standby documentation

2010-02-08 Thread Bruce Momjian
Fujii Masao wrote: > On Mon, Feb 8, 2010 at 10:34 PM, Bruce Momjian wrote: > > Ahh, good point. ?I had not considered the table would change. ?What I > > did was to mark "Slaves accept read-only queries" as "Hot only". > > Can the "warm standby" still reside in v9.0? If not, the mark of > "Hot on

Re: [HACKERS] Hot standby documentation

2010-02-08 Thread Fujii Masao
On Mon, Feb 8, 2010 at 10:34 PM, Bruce Momjian wrote: > Ahh, good point.  I had not considered the table would change.  What I > did was to mark "Slaves accept read-only queries" as "Hot only". Can the "warm standby" still reside in v9.0? If not, the mark of "Hot only" seems odd for me. > I did

Re: [HACKERS] Hot standby documentation

2010-02-08 Thread Bruce Momjian
Markus Wanner wrote: > Bruce, > > Bruce Momjian wrote: > > Ah, I now realize it only mentions "warm" standby, not "hot", so I just > > updated the documentation to reflect that; you can see it here: > > Maybe the table below also needs an update, because unlike "Warm Standby > using PITR", a ho

Re: [HACKERS] Hot standby documentation

2010-02-07 Thread David E. Wheeler
On Feb 7, 2010, at 12:35 PM, Josh Berkus wrote: >> I've always thought this feature was misnamed and nothing has happened >> to change my mind, but it's not clear whether I'm in the majority. > > I'm afraid force of habit is more powerful than correctness on this one. > It's going to be HS/SR whe

Re: [HACKERS] Hot standby documentation

2010-02-07 Thread Josh Berkus
> I've always thought this feature was misnamed and nothing has happened > to change my mind, but it's not clear whether I'm in the majority. I'm afraid force of habit is more powerful than correctness on this one. It's going to be HS/SR whether that's perfectly correct or not. --Josh Berkus

Re: [HACKERS] Hot standby documentation

2010-02-07 Thread Robert Haas
On Sun, Feb 7, 2010 at 4:41 AM, Markus Wanner wrote: > Bruce Momjian wrote: >> Do we want to call the feature "hot standby"?  Is a read-only standby a >> "standby" or a "slave"? > > I think hot standby is pretty much the term, now. See here for the previous iteration of this discussion: http://a

Re: [HACKERS] Hot standby documentation

2010-02-07 Thread Markus Wanner
Bruce, Bruce Momjian wrote: Ah, I now realize it only mentions "warm" standby, not "hot", so I just updated the documentation to reflect that; you can see it here: Maybe the table below also needs an update, because unlike "Warm Standby using PITR", a hot standby accepts read-only queries an

Re: [HACKERS] Hot standby documentation

2010-02-05 Thread Bruce Momjian
Joshua Tolley wrote: -- Start of PGP signed section. > Having concluded I really need to start playing with hot standby, I started > looking for documentation on the subject. I found what I was looking for; I > also found this page[1], which, it seems, ought to mention hot standby. > Comments? > >

Re: [HACKERS] Hot standby documentation

2010-01-13 Thread Simon Riggs
On Thu, 2010-01-07 at 18:34 +0900, Fujii Masao wrote: > On Thu, Jan 7, 2010 at 6:09 PM, Joshua Tolley wrote: > > Having concluded I really need to start playing with hot standby, I started > > looking for documentation on the subject. I found what I was looking for; I > > also found this page[1],

Re: [HACKERS] Hot standby documentation

2010-01-07 Thread Fujii Masao
On Thu, Jan 7, 2010 at 6:09 PM, Joshua Tolley wrote: > Having concluded I really need to start playing with hot standby, I started > looking for documentation on the subject. I found what I was looking for; I > also found this page[1], which, it seems, ought to mention hot standby. > Comments? > >

[HACKERS] Hot standby documentation

2010-01-07 Thread Joshua Tolley
Having concluded I really need to start playing with hot standby, I started looking for documentation on the subject. I found what I was looking for; I also found this page[1], which, it seems, ought to mention hot standby. Comments? [1] http://developer.postgresql.org/pgdocs/postgres/high-availab