| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <josh(at)agliodbs(dot)com>,<tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Summary and Plan for Hot Standby |
| Date: | 2009-11-16 16:07:52 |
| Message-ID: | 4B012478020000250002C8CE@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I agree with Heikki that it would be better not to commit as long as
> any clear showstoppers remain unresolved.
I agree that it would be better not to commit as long as any of the
following are true:
(1) There are any known issues which would break things for clusters
*not using* hot standby.
(2) There isn't an easy way for to disable configuration of hot
standby.
(3) There is significant doubt that the vast majority of the patch
will be useful in the eventually-enabled final solution.
If none of these are true, I'm not sure what the down side of a commit
is.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-16 16:13:23 | Re: Summary and Plan for Hot Standby |
| Previous Message | Pavel Stehule | 2009-11-16 16:04:37 | Re: different result between 8.3 and 8.5 (to_timestamp function) |